Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
dsh Web plugin that aggregates local video and image folders into a streaming media library with Range playback and immersive fullscreen gallery.
- Aggregates local video and image directories into one library
- HTTP Range streaming plus server-side live transcoding
- Mobile-friendly swipe feed with touch gestures and fullscreen wallpaper
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-reelInstall method: npm · runtime verified (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 6 @deepseek-ai/dsh-* packages. raw ranges
>=0.2.0-rc.1 <0.3.0-0 ×6
✓ Running dsh 0.2.1-rc.3 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.1-rc.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 0.2.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.1.2 | · | · | · | · | · |
0.2.0npm✓ 6 runtime-verified2026-10-28
dsh-reel
✓dsh 0.2.1-rc.3current2026-10-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
active in loader tree (150 entries)
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
active in loader tree (150 entries)
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-reel@0.2.0
ID: dsh-reel@0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.2npm✓ 5 runtime-verified2026-09-29
dsh-reel
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-reel@0.1.2
ID: dsh-reel@0.1.2@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
active in loader tree (150 entries)
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-reel@0.1.2
ID: dsh-reel@0.1.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.7-rc.12026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-reel@0.1.2
ID: dsh-reel@0.1.2@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-reel@0.1.2
ID: dsh-reel@0.1.2@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-reel@0.1.2
ID: dsh-reel@0.1.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-reel/?ref=badge)``[](https://www.dsh.so/artifact/dsh-reel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-reel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-reel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-reel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-reel/?ref=badge-install)`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.2.0dsh manifest0.2.0npm2026-10-290.2.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
lib/reel.js:1379const child = spawn( - warningchildProcess · code-exec
lib/reel.js:1744child = spawn(binary, args, { stdio: 'ignore', windowsHide: true }) - warningchildProcess · code-exec
lib/reel.js:1788child = spawn(binary, [ - warningnetIp · network
lib/reel.js:2030log.info('viewer server listening on http://127.0.0.1:%s%s', ownPort, BASE) - warningnetIp · network
lib/reel.js:2600log.info('ready at http://127.0.0.1:%s%s (%s) — no directory configured yet; open it and add one', port, BASE, where) - warningnetIp · network
lib/reel.js:2603log.info('ready at http://127.0.0.1:%s%s (%s) — %s', port, BASE, where, list.map((root) => root.path).join(', '))
show 3 audit findings
- mediumNon-loopback trust fallback accepts any client that echoes Host in Origin/Referer
lib/reel.jsIn a LAN-bound webServer deployment where ctx.get('connection') is absent (or lacks requestRejection), this header comparison is the only non-loopback gate. Origin and Host are both attacker-supplied for a non-browser client, so a curl/script on the LAN can list (/api/list, /api/scan) and download (/stream, /download) every file under the configured roots even though requireTrustedRequest defaults to true; the comment claims this prevents the viewer from becoming a LAN hole.
- lowAll path-containment logic lives in lib/media.js, which could not be reviewed
lib/reel.jsThe plugin's stated security property ("containment is proved, not assumed") is implemented entirely in lib/media.js (assertRelative, resolveInside, streamRange, contentTypeOf, contentDisposition, toWebVtt), which exceeded the harvest limit. A defect there — e.g. realpath containment without a separator boundary, or traversal through decoded %2e%2e segments — would turn every read route into arbitrary-file read; it cannot be verified from this review.
- low/stream and /download serve any file kind under a root, unlike /transcode
lib/reel.jsThe stream route performs no kindOf() gate (contrast /transcode, which rejects anything that is not video/audio). If a configured root happens to contain non-media files — a project folder with .env, .git/config, SSH keys — any client that passes the request fence can fetch them byte-for-byte by constructing the key, even though the viewer is presented as a media gallery.
Local media browser/front-end for dsh; routes are guarded and read-only, but the non-loopback trust fallback is spoofable and containment lives in unreviewed lib/media.js.
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-29 · activity: Stable
• Repo created: 2026-09-12
• Stars: ★ 2 · Forks: 1
• Health: Stable — committed within 90 days
Source
GitHub: github.com/lsjspl/dsh-reel
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-reel?
dsh-reel 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-reel?
Run dsh plugin --profile web add dsh-reel in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-29 (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.