io.github.dingdawg/dingdawg-loop — what this registry has checked

Every record behind those answers

5 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 111 have been across the whole registry.

declared package deprecated (5)

The package registry marks the exact version this entry declares as deprecated.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/dingdawg-governance

Also filed as: io.github.dingdawg, io.github.dingdawg/dingdawg-governance, io.github.dingdawg/dingdawg-legal-agent, io.github.dingdawg/dingdawg-sales-agent, io.github.dingdawg/dingdawg-shield. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 111 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@21826040e38a. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.