Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it does
LibTV canvas and media tools for DeepSeek Harness, with three director skills and one-time QR authorization
Installation
dsh plugin --profile web add github:redkiller79/dsh-libtvInstall method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.3 current |
|---|---|
| 0f979a | ○ |
0f979agithub○ 1 ecosystem plugin2026-10-28
https://github.com/redkiller79/dsh-libtv
○dsh 0.2.1-rc.3current2026-10-28Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/redkiller79/dsh-libtv (version unstated)
ID: dsh-libtv@0f979a@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-libtv/)`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 no conclusion (static stands) → overall low.
v0.1.0dsh manifest0.1.0git2026-10-280.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
lib/oauth.mjs:166spawn(target[0], target[1], { stdio: 'ignore', detached: true }).unref() - warningnetIp · network
lib/oauth.mjs:32const REDIRECT_URI = `http://127.0.0.1:${PORT}/callback` - warningnetIp · network
lib/oauth.mjs:189const url = new URL(req.url || '/', `http://127.0.0.1:${PORT}`) - warningfsWrite · files
lib/oauth.mjs:58fs.writeFileSync(CRED_FILE, `${JSON.stringify(creds, null, 2)}\n`, { mode: 0o600 }) - warningfsWrite · files
lib/oauth.mjs:60fs.chmodSync(CRED_FILE, 0o600)
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
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-10-28
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/redkiller79/dsh-libtv
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
