Integration status
Inspect the package before connecting it to an agent.
An MCP server makes tools available to a client; it does not automatically intercept or govern every action the client can take. The application that performs an effect must enforce identity, permission, consent, and the policy result at the actual action boundary.
Latest registry versions inspected · static artifact review · 2026-10-25
Not independently evaluated for consequential actions
Do not rely on these packages to authorize payments, disclose sensitive data, or perform other consequential actions. The published npm artifacts and their public claims need to be brought into agreement and independently tested. DingDawg has not awarded either package a verified status.
What the current npm artifacts do
The findings below refer to the exact public tarball versions shown, inspected on October 25, 2026. They are a focused static review, not a complete security audit; check the registry again before installing a later version. The independent evaluation state remains NOT_EVALUATED.
npm · dingdawg-governance · v2.1.9
DingDawg Governance
When remote evaluation is absent or fails, the published build falls back to a local keyword heuristic. It can allow actions that do not match its small destructive-word list. Local receipt writes are best-effort, and its badge sets an ipfs_ready field without proving an IPFS record exists.
Review public package and README for dingdawg-governancenpm · dingdawg-loop · v2.0.10
DingDawg Loop
The published build stores schedule metadata and accepts manual evaluation. There is no background scheduler or business-action adapter. Its allowed result is labeled "executed"; that records a decision, not evidence that an external action occurred.
Review public package and README for dingdawg-loopWhat a trusted integration must prove
- Exact package version and artifact digest match the reviewed release.
- Denial, legal-path, timeout, and malformed-response scenarios pass.
- Disabling the gate makes the independent mutation check fail.
- Any receipt is independently verifiable and bound to that artifact and contract.
- Host applications enforce the result before side effects.
- Updates, revocation, recovery, and rollback have tested behavior.
Until that evidence exists, a directory listing, publisher statement, tool response, or package badge is not a security certification.
Explore capability listings