Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Agnes AI image and video generation tools for DSH with cross-process RPM rate limiting, 429 backoff, and local ffmpeg GIF conversion.
- Generates images via the agnes_image tool
- Generates videos via the agnes_video tool
- Cross-process RPM limiting, 429 backoff, ffmpeg GIF conversion
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.
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); the npm pair from every snapshot.
5 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-30 · 5 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 10-30 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-26 → 11-03 · 36 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-26 → 11-04 · 37 points
Installation
dsh plugin --profile web add dsh-agnes-genInstall method: npm · sandbox install ok, web smoke failed (L5)
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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.6-alpha.2 || ^0.1.7-alpha.1 || ^0.2.0-rc.1 ×1
✓ Running dsh 0.2.2-rc.1 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 0.1.3 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 0.1.2 | · | · | · | · | · |
| 0.1.1 | · | · | · | · | · |
| v0.1.1 | · | · | · | · | · |
0.1.3npm8 failed2026-11-05
dsh-agnes-gen
✗dsh 0.2.2-rc.1current2026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.32026-10-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.42026-10-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-agnes-gen@0.1.3
ID: dsh-agnes-gen@0.1.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.2npm1 failed2026-10-01
dsh-agnes-gen
✗prehistory2026-10-01L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-agnes-gen@0.1.2
ID: dsh-agnes-gen@0.1.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.1npm2 failed2026-09-29
dsh-agnes-gen
✗dsh 0.2.0-rc.12026-09-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-agnes-gen@0.1.1
ID: dsh-agnes-gen@0.1.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-agnes-gen@0.1.1
ID: dsh-agnes-gen@0.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.1github2026-09-23
https://github.com/Ylhow06/dsh-agnes-gen
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-agnes-gen/?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 low; dynamic medium (authoritative when present) → overall medium.
v0.1.3dsh manifest0.1.3npm2026-11-050.1.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningfsWrite · files
lib/client.js:159fs.writeFileSync(file, buf); - warningfsWrite · files
lib/client.js:335fs.writeFileSync(file, Buffer.from(item.b64_json, "base64")); - warningchildProcess · code-exec
lib/gif.js:19const r = spawnSync(ffmpeg, ["-hide_banner", "-loglevel", "error", "-nostdin", "-y", ...args], { - warningchildProcess · code-exec
lib/gif.js:49const probe = spawnSync(cmd, ["-version"], { stdio: "ignore" }); - warningchildProcess · code-exec
lib/gif.js:99const probe = spawnSync(cmd, ["-version"], { encoding: "utf8" }); - warningfsWrite · files
lib/rate-limit.js:124fs.writeFileSync(file, JSON.stringify(times)); - warningfsWrite · files
lib/rate-limit.js:127fs.writeFileSync(file, JSON.stringify(times)); // 顺手把过期记录写回去
show 4 audit findings
- mediumReference-image arguments are read from disk and base64-uploaded to the third-party Agnes API
lib/client.js:285The image/first_frame/last_frame tool parameters are model-supplied paths (see index.js: '参考图路径或公网 URL ... 本地路径相对当前工作目录解析'). At this call site there is no extension, size or allow-list check before the file is base64-encoded into the outbound POST body, so a prompt-injected agent can name any file the host process can read (e.g. the workspace .env, id_* keys) and have its content transmitted to agnes-ai.cn / apihub.agnes-ai.com. This is an undisclosed egress channel rather than a functional bug.
- lowffmpeg filtergraph built by raw string interpolation of gif_width/gif_fps without numeric coercion
lib/gif.js:164width/fps come from the tool args (declared integer) and from settings and are spliced into a single -vf string with no Number()/clamp. The arguments are passed as an argv array (no shell), so there is no command injection; however, if upstream parameter typing is bypassed, extra filtergraph syntax (e.g. movie=/path or drawtext=textfile=/path) could be smuggled into -vf and rendered into the output GIF.
- lowDownload URL taken verbatim from API response without scheme/host validation
lib/client.js:156download() is called with item.url (image result) and info.metadata.url ?? info.url (video result). A compromised or spoofed API response can point the fetch at loopback or LAN addresses (SSRF from the host) and the response body is written into outDir and its path returned to the model. Only the file extension is derived from the URL.
- lowRate-limit state written to a predictable path under the shared temp directory
lib/rate-limit.js:130file resolves to path.join(os.tmpdir(), "agnes-ratelimit", "bucket-<bucket>.json") (line 101/105) and is written with plain writeFileSync, which follows symlinks. A local attacker able to pre-create that directory or a symlink inside it can redirect the write to any file the user can write (contents are only JSON timestamps/host state, so impact is limited).
No critical/high issues: secrets handling, hosts and argv-style ffmpeg use are sound; one medium data-egress path (local files uploaded as reference images) plus three low hardening gaps.
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-09-30 · activity: Stable
• Repo created: 2026-09-22
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/Ylhow06/dsh-agnes-gen
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 @Ylhow06/dsh-agnes-gen?
@Ylhow06/dsh-agnes-gen 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 @Ylhow06/dsh-agnes-gen?
Run dsh plugin --profile web add dsh-agnes-gen 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-11-05 (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.