Is Dingdawg Compliance safe and trustworthy?

tashan scores Dingdawg Compliance on public evidence — tashan score 48.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Dingdawg Compliance?

In Claude Code: run `claude mcp add dingdawg-compliance -- npx -y dingdawg-compliance`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Dingdawg Compliance?

source: DingDawg-dev/dingdawg-compliance.

‹ The Index

Dingdawg Compliance

npm

EU AI Act + Colorado AI Act compliance scoring. 87/100 in 60 seconds. Free local scan.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Security — see all ranked ›

Work: Regulatory compliance

Who it is for: Legal / compliance · Security engineer

Install (Claude Code):

claude mcp add dingdawg-compliance -- npx -y dingdawg-compliance

deep

“Shows real scan output and says what it does not include; installs via pip, not npm.”

This grade is wrong ›

tashan score: 48.0
Instruction depth: 82.0 (deep — documents every tool, with worked examples, setup and a stated limitation)
Adoption: 88/wk
Upkeep: 63.0
Freshness: 80.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: BUSL-1.1

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 2.0.15 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Dingdawg Compliance scores 48 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-dingdawg-compliance.svg)](https://tashan.sh/capability/pkg-dingdawg-compliance.html)

npm ↗ · source ↗ · pkg:dingdawg-compliance

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?