Plugin audit
How we audit every plugin
Verified means L1 install + L2 load + L3 headless on dsh 0.1.0-rc.8; if L3 is web-only, L4 web CDP is mandatory. Not a topic count or a parseable-manifest badge.
Web L4 verification progress
Web-only (GUI / browser-dependent) plugins: 738 total · verified (passed L4 CDP) 738 · awaiting L4 / not passed 0. A web-only plugin must pass L4 (web CDP) to be verified.
Data current as of 2026-09-29 · recalculated on every build from the live plugin dataset.
What Verified means
Listing answers “does this belong here?” Verification answers “does it actually work?” Other catalogs sometimes label “verified” when a plugin is merely installable from a manifest. Here:
- L1 · Install — the plugin is installed into a clean profile alongside a pinned DSH runtime.
- L2 · Load — the profile boots and dumps its configuration successfully.
- L3 · Headless — a headless question is answered with the plugin loaded. If the plugin is GUI-only, L3 returns web-only — that is not a pass.
- L4 · Web CDP — required when L3 is web-only: boot a web profile and run browser CDP Q&A. Only L4 ok upgrades to verified.
verified— L3 headless ok, or L3 web-only + L4 CDP ok.pending— listed but not yet passed (including web-only waiting on L4, or a prior failure — see the note).- Trust tier is supplementary; stars are popularity only.
Three audits before listing
Each entry is checked before it appears in the directory.
1 · Source audit
Every entry must map to a real, reachable GitHub repository. Renamed, deleted, or unreachable repositories are removed.
2 · Ecosystem audit
DSH-specific manifests (cordis.patch.yml, dsh.bundle, …) and DSH dependencies — not just a repo name or topic tag.
3 · Metadata audit
License, stars, forks, issues, last-updated date, language, and archived status on every card.
Pending & failure browser
0 plugins are currently pending. Filter by failure class parsed from the catalog note (live data — not the August batch snapshot below). Awaiting L4 means L3 returned web-only and CDP has not passed yet; L4 failed means CDP already ran and failed. Old notes like “web L3 … CDP E2E” are ordinary install/load/runtime fails — not an L4 queue.
| Plugin | Class | Last test | Note |
|---|
Full verification run — August 2026
Batch snapshot from the first full three-stage pass over then-pending entries.
Results
Why the rest did not pass (batch)
Install failures (159)
- 68 — declared dependency version does not exist on the registry
- 63 — build / prepare script failed (often a dependency on an unpublished @deepseek-ai/* package)
- 15 — dependency package or repository returns 404
- 13 — unsupported dependency structure (workspace / linked / exotic)
Runtime failures (182)
- 107 — plugin entry failed to activate at boot
- 70 — loader entry failed to apply (unsupported schema DSL, missing config, version mismatch)
- 5 — other
Load failures (10)
- 10 — overlay file missing (ENOENT)
Our stance on reliability
- Listing is not endorsement.
- We audit continuously — intake verify plus regular re-checks.
- Honest and reproducible — manifests, repository state, and actual test results.
Found a wrong entry? Tell us, or open an issue. Browse the plugin guide.