io.github.dingdawg/dingdawg-governance
NPM · DINGDAWG-GOVERNANCE
Universal governance layer for AI agents. MCP-native, fail-closed, audit proofs and rollback.
Available components
Last scanned (21 hours ago)
Scores higher than 63% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency26
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 894 tokens (~127/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −1
- Stability: pass → 0.90 functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/dingdawg-governance@2.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_trail ~91
Get the governance audit trail. Returns governance receipts from local storage or cloud API. Free to use.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent ID to get all governed actions for |
| limit | number | – | Maximum number of records to return (default 10) |
| receipt_id | string | – | Receipt ID from a govern_action call |
| time_range | string | – | Time range for audit trail lookup |
No output schema declared.
No examples provided.
compliance_check ~116
Quick compliance check against common AI governance frameworks. Free tier: 10 checks per day. Evaluates against EU AI Act, Colorado AI Act — Revised (SB26-189 / ADMT, eff. Jan 1 2027), NIST AI RMF, and ISO 42001.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_stage | string | – | Current deployment stage |
| framework | string | – | Framework to check against (default: all) |
| system_description | string | yes | Describe your AI system: what it does, data sources, decision scope |
No output schema declared.
No examples provided.
get_spend_report ~123
Get LLM spend breakdown by agent, model, and provider. Filter by agent and date range. Returns total cost, call count, and per-model breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Filter by agent ID (omit for all agents) |
| from_date | string | – | ISO 8601 start date (e.g. '2026-04-01T00:00:00Z') |
| to_date | string | – | ISO 8601 end date (e.g. '2026-04-30T23:59:59Z') |
No output schema declared.
No examples provided.
get_verified_badge ~98
Returns the 'Powered by DingDawg Verified' badge payload for a governed action receipt. Creators can opt-in to emit this badge in agent output — every governed action receipt includes a verifiable badge URL, turning governed agents into DingDawg marketing channels. Pass the receipt_id returned by govern_action.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | Receipt ID returned by a govern_action call (e.g. 'gov_abc123_def456') |
No output schema declared.
No examples provided.
govern_action ~173
Govern any AI agent action. Performs capability check + policy evaluation + generates a governance receipt. Returns a receipt proving the action was governed. When API key is set, uses cloud API with local fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| action_description | string | yes | Human-readable description of what the agent is about to do |
| action_type | string | yes | Type of action (e.g., 'send_email', 'make_purchase', 'modify_data', 'api_call') |
| agent_id | string | yes | Identifier for the AI agent performing the action |
| context | object | – | Additional context key-value pairs for policy evaluation |
| risk_tier | string | – | Self-assessed risk level of this action |
| target_resource | string | – | The resource being acted upon (e.g., 'user_database', 'email_server', 'payment_api') |
No output schema declared.
No examples provided.
meter_llm_call ~166
Track the cost of an LLM API call and enforce budget limits. Call this after every LLM API response. Returns real-time cost, cumulative spend, and budget status. Free to use — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Unique identifier for the agent making the LLM call |
| completion_tokens | integer | yes | Number of output/completion tokens generated |
| model | string | yes | Model name (e.g. 'gpt-4o', 'claude-sonnet-4-6', 'gemini-2.0-flash') |
| prompt_tokens | integer | yes | Number of input/prompt tokens used |
| provider | string | yes | LLM provider |
| task_id | string | – | Optional task identifier for grouping related calls |
No output schema declared.
No examples provided.
set_llm_budget ~127
Set a USD spend limit for an agent. The meter will return budget_status: 'warning' at the threshold and 'exceeded' when the limit is hit. Limits reset daily or monthly.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent ID to set budget for |
| limit_usd | number | yes | Maximum USD spend allowed in the period (e.g. 10.00 for $10/day) |
| period | string | yes | Reset cadence |
| warning_threshold | number | – | Fraction of limit that triggers 'warning' status (default: 0.8 = 80%) |
No output schema declared.
No examples provided.
How do I install the io.github.dingdawg/dingdawg-governance MCP server?
io.github.dingdawg/dingdawg-governance runs locally as an npm package, launched with npx -y dingdawg-governance. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dingdawg-governance
claude mcp add dingdawg-dingdawg-governance -- npx -y dingdawg-governance
What is the io.github.dingdawg/dingdawg-governance MCP server?
io.github.dingdawg/dingdawg-governance is an MCP server listed in the public MCP registry as io.github.dingdawg/dingdawg-governance. Universal governance layer for AI agents. MCP-native, fail-closed, audit proofs and rollback. This page covers its npm package (dingdawg-governance).
Is the io.github.dingdawg/dingdawg-governance MCP server safe to use?
io.github.dingdawg/dingdawg-governance scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dingdawg/dingdawg-governance MCP server expose?
io.github.dingdawg/dingdawg-governance exposes 7 tools: govern_action, get_verified_badge, audit_trail, compliance_check, meter_llm_call, and 2 more. Their descriptions and schemas cost roughly 894 tokens of context every time the server is loaded.
Is the io.github.dingdawg/dingdawg-governance MCP server still maintained?
io.github.dingdawg/dingdawg-governance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dingdawg/dingdawg-governance MCP server under?
io.github.dingdawg/dingdawg-governance declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the io.github.dingdawg/dingdawg-governance MCP server?
VerifyMCP ran 16 checks on io.github.dingdawg/dingdawg-governance, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.