dsh-xray — capability cards for DeepSeek Harness plugins

What a dsh plugin declares vs. what its code actually does — with file:line evidence.

English · 简体中文

🔍 Registry · 📊 Report · 📈 Levels explained · 📖 How dsh plugins work

Site available in English / 简体中文 / 日本語

90% of scanned plugins carry a powerful capability surface · 80% patch the dsh runtime itself · 10,645 plugins scanned, refreshed daily

Why

The dsh-plugin ecosystem went from ~200 to 10,900+ repos in little over a month. Plugins run arbitrary code inside your agent runtime: they can rewrite your system prompt (system-prompt/assemble), intercept every API call (api/gate), spawn subprocesses, read GITHUB_TOKEN from your env, and even patch the runtime itself (manifest.bundle.patch). Today nothing surfaces any of that before you install.

dsh-xray statically scans every plugin in the ecosystem and publishes a capability card:

Every flag carries file:line evidence. Levels C0–C3 measure capability surface and transparency — not maliciousness. A C3 plugin can be perfectly legitimate; you just deserve to know before it touches your agent.

Features

• Whole-ecosystem coverage — every repository under the dsh-plugin topic (10,915), rescanned daily.
• Capability cards — injected services, attached hooks, runtime patches, outbound domains, credential-class env reads and install-time scripts, each with file:line evidence.
• C0–C3 levels — a compact read on how much surface a plugin has, and whether it combines powerful capability with sensitive behavior.
• Shipped vs. unshipped code — risk flags fire only on code that reaches your runtime, so a fixture in tests/ never inflates a rating, and neither does a build script the package's own files allowlist keeps out of the tarball. Both stay on the card as non-counting evidence.
• Deterministic manifests — in a monorepo the plugin's own root manifest wins, so two scans of one repo agree.
• Static only — nothing is executed, downloaded code is streamed and read, never run.
• Embeddable badges — plugin authors can publish their own capability card.
• Trilingual site — English, 简体中文, 日本語, plus a crawlable page per plugin.

Capability levels

C0 no notable surface · C1 ordinary (tools, services, outbound domains) · C2 powerful: prompt surface, API interception, subprocess, exec, credential reads or install scripts · C3 powerful capability combined with sensitive behavior.

Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. See the levels explained visually.

Use it inside dsh

dsh-xray-plugin puts the lookup where the question comes up — in the agent, while you are deciding whether to install something.

dsh plugin add https://github.com/unStone/dsh-xray-plugin/releases/download/v0.1.0/dsh-xray-plugin-0.1.0.tgz

Is tt-a1i/archify safe to install?

Audit the plugins I have installed.

Badge

Plugin authors: show users your capability card.

[![dsh-xray](https://img.shields.io/endpoint?url=https%3A%2F%2Funstone.github.io%2Fdsh-xray%2Fbadge%2F<owner>__<repo>.json)](https://unstone.github.io/dsh-xray/registry.html#<owner>__<repo>)

Run it yourself

python scanner/discover.py all           # enumerate topic:dsh-plugin (needs gh auth)
cd scanner && python pipeline.py all 24  # download + scan, no git clone
python render_report.py                  # inject current figures into the report
python render_pages.py                   # plugin pages, collections, sitemap, feed

Outputs: data/scans/*.json (full cards), docs/data.json (site data), docs/badge/*.json (shields endpoints), docs/p/*.html (a page per plugin). A daily GitHub Action refreshes all of it.

Methodology & fair play

• Static analysis only; nothing is executed.
• Shipped code and test/dev code are classified separately; risk flags fire on shipped code only.
• False positive? Open an issue — cards link evidence so disputes are checkable, and rules get fixed in public.

Roadmap

• Full-ecosystem coverage — 10,915 repositories, rescanned daily
• Daily diff feed: what changed in the capability surface of plugins you use
• cordis.patch.yml runtime-patch audit view
• Companion plugin: look plugins up from inside dsh
• Multi-harness: Abu-Cowork & Claude Code plugin formats
• Private registry / org policy engine (enterprise)

License

Apache-2.0 — see LICENSE. The scan data under data/ and docs/ is published under the same terms.

Changelog

What changed and why — method and product changes; scan results refresh daily on their own.