This entry has been merged into: dsh-harmony-2 — verification records were moved there; this page is kept as an archive.
Install verification: sandbox install passed (L4) · runtime test (L5) pending · tested on dsh 0.1.1-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
A library for patching, replacing and decorating dsh plugins during runtime.
- Patch dsh plugins at runtime
- Replace plugin implementations
- Decorate plugin behavior
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add dsh-harmony@0.8.8security scan passed · npm package v0.8.8
Install method: npm · sandbox install passed (L4) · runtime test (L5) pending · verified on dsh 0.1.1-rc.2
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
current (registry 2026-10-30) · 0 samples; a smoothed curve through every sample — not a daily series
Only 0 points (< 3): no chart yet
no data yet
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
Only 0 points (< 3): no chart yet
no data yet
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
08-17 → 08-26 · 7 points
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.1.1-rc.2 |
|---|---|
| 0.8.3 | · |
| 0.8.1 | · |
0.8.3npm2026-08-24
dsh-harmony
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.8.1npm2026-08-22
dsh-harmony
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-harmony/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static high; dynamic low (authoritative when present) → overall low.
v0.8.8dsh manifest0.8.8npm2026-08-25v0.8.19version moved onsuspicious · npmVet is an AST static scan (npm artifact or git source).
show 1 audit findings
- lowGlobal-install postinstall imports an unreviewed script
package.json:103On global npm install, Node dynamically imports scripts/postinstall.cjs with the installer's privileges; that file is absent from the harvested source, so its behavior cannot be verified.
Harvested code is benign; one low-risk gap remains: the global-install postinstall imports an unreviewed script.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-28 · activity: Active
• Repo created: 2026-08-14
• Stars: ★ 21 · Forks: 2
• Health: Active — committed within last 30 days
Source
GitHub: github.com/CH4ACKO3/dsh-harmony
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is dsh-harmony?
dsh-harmony is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install dsh-harmony?
Run dsh plugin --profile web add dsh-harmony@0.8.8 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-10-30 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.