Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Browse 6,454 Hacker News-curated technical videos in a panel with Chinese titles, AI Q&A over transcripts, and HN discussions.
- Panel to explore 6,454 top-rated tech videos picked by Hacker News
- Chinese titles plus AI Q&A over video transcripts
- Jump into the original HN discussion threads for each video
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-hackertubeInstall 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| 0.3.0 | ✓ |
| v0.1.6 | · |
0.3.0npm✓ 1 runtime-verified2026-11-10
dsh-hackertube
✓dsh 0.2.2-rc.1current2026-11-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-hackertube@0.3.0
ID: dsh-hackertube@0.3.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-10 · expires: 2026-11-17
View checks & evidence
↳ carried from earlier record dsh-hackertube@3f6ecd@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-hackertube@3f6ecd@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-hackertube@3f6ecd@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.6github2026-11-10
https://github.com/chow651/dsh-hackertube
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-hackertube/?ref=badge)``[](https://www.dsh.so/artifact/dsh-hackertube/?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 high; dynamic medium (authoritative when present) → overall medium.
v0.4.1dsh manifest0.4.1npm2026-11-110.4.1same versionsuspicious · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
index.js:1358const child = spawn('yt-dlp', args, { windowsHide: true }) - warningchildProcess · code-exec
index.js:1480const ytdlp = spawn( - warningchildProcess · code-exec
index.js:1496const ff = spawn( - warningnetIp · network
index.js:1391const relayOrigin = /^[\w.:-]+$/.test(host) ? 'http://' + host : 'http://127.0.0.1:18090' - warningnetIp · network
index.js:4153state.mediaOrigin = `http://127.0.0.1:${port}`
show 4 audit findings
- mediumUntrusted video subtitles and HN metadata are concatenated into the LLM system prompt
index.jsVideo summaries, HN 'why_hn' text and yt-dlp subtitles come from third parties (hackertube.org export / any YouTube video). Their content is inserted verbatim into the system prompt, so a video author or data contributor can embed instructions that steer the assistant's answer shown in the panel (e.g. phishing or manipulated guidance). No delimiting or instruction-hierarchy isolation is applied.
- lowUnauthenticated loopback media server triggers yt-dlp/ffmpeg and is reachable via DNS rebinding
index.jsThe second server performs no origin or Host validation (unlike trusted()), so any local process, or a malicious web page using DNS rebinding, can request /stream or /media for arbitrary regex-valid IDs, spawning yt-dlp/ffmpeg downloads and consuming disk/network. Impact is limited to resource/network abuse and fetching arbitrary public YouTube media, but it is an unauthenticated local attack surface.
- lowHardcoded Google Translate key with automatic third-party egress of titles, summaries and comments
index.jsComment text, video titles/summaries and recommendations are sent to googleapis.com translate endpoints automatically during translation. The key is a shared public web key, so this is not a credential leak, but it is an undisclosed data-egress channel to a third party.
- lowAuthenticated launch-token URL persisted to cache and returned by /config
index.jsA launch-token-bearing URL that authenticates to the DSH web UI is written in plaintext to the cache directory and exposed via /config. It is gated by the trusted() host/origin check and the webServer auth layer, so exposure is limited to authenticated/local clients, but the token at rest is a hardening gap.
Host plugin validates video IDs before spawning yt-dlp/ffmpeg and whitelists zip extraction, but feeds untrusted video content into an LLM prompt and runs an unauthenticated loopback service.
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-11 · activity: Active
• Repo created: 2026-11-05
• Stars: ★ 7 · Forks: 1
• Health: Active — committed within last 30 days
Source
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 @chow651/dsh-hackertube?
@chow651/dsh-hackertube 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 @chow651/dsh-hackertube?
Run dsh plugin --profile web add dsh-hackertube 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-11-11 (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.