Evidence status

Evidence starts with the exact artifact.

This page records focused static artifact reviews of four published npm packages. The versions and digests identify exactly what was inspected; they do not certify that an action was safe or executed.

Scope and status

NOT_EVALUATED for consequential use

This focused static artifact review is not a full security audit, runtime test, certification, or proof of an external action. The tarballs were fetched anonymously and inspected as temporary archive contents; they were not installed or executed. Findings apply only to the exact versions and digests below; check the registry before installing a later release. Do not rely on these packages to authorize payments, disclose sensitive data, or perform another consequential action.

Reviewed published artifacts

Each version matched its npm latest tag on 2026-10-25. Local candidate source versions are not substituted for what registry users receive; the tag is not refreshed on each page request.

Published npm artifact · reviewed 2026-10-25

dingdawg-governance@2.1.9

NOT_EVALUATED

Focused static artifact review of anonymous npm tarball bytes. Not a complete security audit, runtime test, independent evaluation, certification, or proof of an external action. Registry currentness is not checked at request time.

npm latest tag at review: 2.1.9 on 2026-10-25. This is a dated observation, not a live registry check.

Observed in this artifact review

  • If remote evaluation is absent or fails, this release falls back to a local keyword heuristic; unrecognized actions can receive allow.
  • The badge payload sets ipfs_ready, but the inspected client does not establish that a corresponding IPFS record exists.
  • A local receipt write failure is caught rather than failing the evaluation response.
npm tarball SHA-256
7b76053598d2896b71f3aa2f5801f76dec2de1ce291ec5ae5294313079029d1a
Shipped dist/index.js SHA-256
cddfbdc1e194bfc0c515631ab788c77f377ce99412f0c3a3a72343f7eb76b25c
Inspect this exact npm version

Published npm artifact · reviewed 2026-10-25

dingdawg-loop@2.0.10

NOT_EVALUATED

Focused static artifact review of anonymous npm tarball bytes. Not a complete security audit, runtime test, independent evaluation, certification, or proof of an external action. Registry currentness is not checked at request time.

npm latest tag at review: 2.0.10 on 2026-10-25. This is a dated observation, not a live registry check.

Observed in this artifact review

  • Schedules are stored as metadata; the inspected release has no background scheduler.
  • The published server evaluates an intention and records a result; it does not dispatch the described business action.
  • An allowed result is labeled executed, which is not evidence that an external effect occurred.
npm tarball SHA-256
7c762d23e09db5dd69654b9e9a23b344a44648e24a8f154e3604815a42abec5c
Shipped dist/index.js SHA-256
71e5efb0c34aabb8ba37e3d7c9b925d66bfa1cd46b6eb54addca7da4691f0877
Inspect this exact npm version

Published npm artifact · reviewed 2026-10-25

dingdawg-agent-wallet@1.0.7

NOT_EVALUATED

Focused static review of the anonymous registry-latest npm tarball, shipped runtime entry point, package manifest, and README. It is not a complete audit, runtime test, independent evaluation, or proof that the wallet provider enforces any policy. Registry currentness is not checked at request time.

npm latest tag at review: 1.0.7 on 2026-10-25. This is a dated observation, not a live registry check.

Observed in this artifact review

  • Any non-empty approval_token satisfies the step-up gate; this artifact does not verify who issued the token, its signature, expiry, or whether it is bound to this wallet, amount, and recipient.
  • The governed_spend input schema and implementation do not enforce a positive amount. A negative amount passes the shown upper-bound comparisons and is added to daily spend, reducing the local recorded total before returning an authorization-shaped AgentKit call.
  • The receipt chain is stored in a local writable JSONL file; this release does not externally anchor or make that file immutable. The README describes tamper evidence, not an independent settlement proof.
npm tarball SHA-256
7b7367e7336890ca6df6e517be4aa1625623497b0c5923546c081f90aebfa918
Shipped dist/index.js SHA-256
216d28c89bdbf24c622e09f2f4be4b7a1aa362abd69b238e03f763e6938fc8d3
package.json SHA-256
b33c2034cf2511c4887f758c230a4b5f997c4318ef5a3b2306c8fd8603fe508a
README.md SHA-256
87e1762d06eef9aa32bd60119f13d731b7b3a6a56269ae21273228956c40a1d9
Inspect this exact npm version

Published npm artifact · reviewed 2026-10-25

dingdawg-payments@1.0.2

NOT_EVALUATED

Focused static review of the anonymous registry-latest npm tarball, shipped runtime/store files, package manifest, and README. It is not a complete audit, runtime test, independent evaluation, or proof of an on-chain settlement. Registry currentness is not checked at request time.

npm latest tag at review: 1.0.2 on 2026-10-25. This is a dated observation, not a live registry check.

Observed in this artifact review

  • payment_receipt does not compare its caller-supplied amount, recipient, or tool_used with the stored authorization. It deducts the supplied amount and records the caller-supplied settlement details as AUTHORIZED.
  • The receipt path accepts a supplied payment_hash but does not query a chain or payment provider to confirm that settlement occurred or matches the authorized transaction.
  • authorize_payment does not reserve budget; multiple outstanding authorizations can each pass against the same remaining balance before receipts are finalized.
  • Local JSON persistence catches and suppresses write errors, so tools can return success when authorization, budget, or receipt state was not durably saved.
  • An unknown caller-provided agent_id is automatically assigned a fresh default budget. The MCP server code does not bind that identifier to an authenticated principal or team identity.
  • The package manifest exposes the executable as dingdawg-payments, while the README instructs users to install and run dingdawg-x402-pay.
npm tarball SHA-256
72f9d0d6560f34c859ae26df4c0467bcf7c29bc0e5490cb291b5a04a7d536ac0
Shipped dist/index.js SHA-256
ffef7332eb4168e502002d94df9e0856de8faccba015bcdf58295f7d0c89d8e7
dist/store.js SHA-256
e1fab33290d750fdc4bec1c9a82b57a3b595718b62a3c6996c9041017d6ffe32
package.json SHA-256
98f1345d22bf4383ce49ce730039c82b8c0b733f0b106b09f0c441967591e315
README.md SHA-256
14909f22c1356755e8bce056aacbe8159ee9b16d5cd4073ebe288de198280bdd
Inspect this exact npm version

What verified status still requires

  • Independent tests against the exact version and digest.
  • Legal-path, denial, outage, malformed-response, and recovery cases.
  • A mutation check proving the safety gate cannot be disabled unnoticed.
  • Host-side enforcement before the real-world effect.
  • Receipts bound to the artifact and policy, with verification and revocation behavior.
  • Current evidence after updates; stale evidence cannot keep a verified state.

A marketplace listing, publisher description, badge, or tool response does not replace these checks. Community submissions remain untrusted until independently evaluated.