dsh-plugins avatar

dsh-plugins

Generic DeepSeek Harness (dsh) plugins: A2A protocol server, session storage mirror, and Langfuse observability.

Ecosystem appAI ModelsNetworkStorageStorage
Verification
L5 · Ecosystem app
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →

Data as of (UTC)

What it doesAI

Offers DeepSeek Harness plugins for A2A agent protocol, session storage mirroring, and Langfuse observability.

  • A2A protocol server for agent-to-agent communication
  • Session storage mirror for persisting sessions
  • Langfuse integration for observability and tracing
aiAIstorageAI

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

GitHub repository

Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).

The level reads L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the ladder does not rate them); the security scan still runs.

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.

GitHub stars
7★

current (registry 2026-11-19) · 9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-22 → 11-05 · 9 points

Weekly star gain
+2★

Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend

09-28 → 11-05 · 8 points

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
—

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

Only 0 points (< 3): no chart yet

no data yet

weekly board —total board —downloads ≠ unique usersstar weekly —

Verification & Compatibility◼ Ecosystem app

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
◼ Ecosystem app
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.2-rc.3dsh 0.2.2-alpha.2dsh 0.2.1-rc.5dsh 0.2.1-rc.3dsh 0.2.1-alpha.4
v0.1.44·····
v0.1.43·····
v0.1.42·····
v0.1.38·····
v0.1.34·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v0.1.44github2026-11-15

https://github.com/TGYD-helige/dsh-plugins

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.1.43github2026-11-14

https://github.com/TGYD-helige/dsh-plugins

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.1.42github2026-11-09

https://github.com/TGYD-helige/dsh-plugins

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.1.38github2026-11-04

https://github.com/TGYD-helige/dsh-plugins

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

v0.1.34github2026-10-30

https://github.com/TGYD-helige/dsh-plugins

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

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:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-plugins-53.svg)](https://www.dsh.so/artifact/dsh-plugins-53/?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.

dsh-plugins-53Automated review · daily

Static low; dynamic low (authoritative when present) → overall low.

static low→dynamic low→overall low
dynamic findings0 critical·0 high·0 medium·0 low
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin version—
scanned versionv0.1.44git2026-11-19
current versionv0.1.44same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

2model reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-11-10
audited artifactgit 49b13c46f6a8b0a995863019eab260352be80ab8

The artifact has changed (audited git 49b13c46f6a8b0a995863019eab260352be80ab8 → current git 438b4833668f10cd5c0e734ea2ac71a6948bc7ee): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.

findings0 critical·0 high

Only manifests and CI test scripts were supplied; no reachable risky construct found, and the plugin's core src/index.ts was not available to audit.

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-11-18 · activity: Active

• Repo created: 2026-08-19

• Stars: ★ 7 · Forks: 2

• Health: Active — committed within last 30 days

Source

GitHub: github.com/TGYD-helige/dsh-plugins

Frequently asked questions

What is dsh-plugins?

dsh-plugins is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.

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-plugins?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.

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-11-19 (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.

Was this page helpful?