The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
First-run health check for DeepSeek Harness (dsh): verifies Node/pnpm/dsh toolchain, profile, API key (names only), workspace and registry, then prints actionable next steps. Zero runtime deps, read-only. CLI + agent-callable quickstart tool.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-alpha.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
First-run health check for DeepSeek Harness validating toolchain, profile, API key, workspace, and registry.
- Verifies Node, pnpm, and dsh toolchain
- Checks profile, API key names, workspace and registry
- Zero runtime deps, read-only, prints actionable next steps
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 github:zoahdev/dsh-firstrun#v0.1.0Install method: GitHub · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.1-alpha.2
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.
4 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 10-09 · 4 points
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-24 → 10-09 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
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.0-rc.6 ×1
✗ Running dsh 0.2.2-rc.5 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-firstrun@0.1.0 0.2.2-rc.5 (the exemption lives in the local profile; this site does not assume one)
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-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ | ✗ | · |
v0.1.0github11 failed2026-10-12
https://github.com/zoahdev/dsh-firstrun
✗dsh 0.2.1-alpha.22026-10-12L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@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.
✗dsh 0.2.0-rc.12026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.22026-09-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.12026-09-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-rc.12026-09-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/zoahdev/dsh-firstrun#v0.1.0
ID: dsh-firstrun@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
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-firstrun/?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 low (authoritative when present) → overall low.
v0.1.0dsh manifestv0.1.0git2026-10-12v0.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalspawnShell · shell
src/quickstart.ts:53const result = spawnSync(commandLine, { encoding: 'utf8', timeout: 10_000, windowsHide: true, shell: true }) - warningnetIp · network
scripts/dsh-smoke.sh:32if curl -sf http://127.0.0.1:4099 >/dev/null 2>&1; then - warningchildProcess · code-exec
src/quickstart.ts:53const result = spawnSync(commandLine, { encoding: 'utf8', timeout: 10_000, windowsHide: true, shell: true }) - warningchildProcess · code-exec
src/quickstart.ts:56const result = spawnSync(cmd, args, { encoding: 'utf8', timeout: 10_000 })
show 3 audit findings
- lowWindows code path uses spawnSync with shell:true (not reachable with attacker input)
src/quickstart.ts:53A shell-string invocation is a classic command-injection shape, but every caller passes hardcoded literals ('node'/'pnpm'/'dsh' with ['--version'], 'npm' with ['config','get','registry']); no env var, tool argument or file content reaches cmd/args, and the custom quoteArg is input-independent in practice. No exploitable path exists; this is a hardening gap only (a fully correct Windows quoting/escaping rule is not implemented).
- lowTool caller can probe presence of arbitrary environment variable names
src/index.ts:81The 'quickstart' tool parameter (src/index.ts:62, additionalProperties:true, unsanitised array) overrides the allowlisted API-key names, so an agent (or a prompt-injected model) can ask whether any env var, e.g. AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN, is set and get the chosen name echoed back in the report. Only a boolean presence bit is exposed — values are never read or printed — so impact is limited to environment reconnaissance inside an already-compromised agent session.
- lowDev-only smoke script executes unpinned packages via pnpm dlx
scripts/dsh-smoke.sh:22The script downloads and runs whatever @deepseek-ai/dsh resolves to at execution time (also a local web server on port 4099), so a compromised or re-tagged registry version runs with developer privileges. scripts/ is excluded from the published npm 'files' list, so end users are unaffected; risk is limited to maintainer/CI machines.
Static-scan critical refuted: shell:true only runs hardcoded commands; remaining issues are low-severity (arbitrary env-name probing, unpinned dlx in a dev-only script).
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-08-18 · activity: Inactive
• Repo created: 2026-08-18
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/zoahdev/dsh-firstrun
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-firstrun?
dsh-firstrun 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-firstrun?
Run dsh plugin --profile web add github:zoahdev/dsh-firstrun#v0.1.0 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-10-17 (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.
