Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · 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 environment self-check plugin that shows installed system/CLI/DSH plugin status, secret presence, and frees stuck dev ports via a dashboard.
- Card dashboard for system, CLI, DSH plugin and key presence checks
- One-click release of dev ports left occupied by stale processes
- Zero runtime dependencies; network checks only on click, no plaintext secrets
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.
9 samples (roughly every 7 days), 5 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-31 · 9 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-30 → 10-31 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-25 → 11-03 · 38 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-25 → 11-04 · 38 points
Installation
dsh plugin --profile web add @dsh-plugins/dsh-env-inspectorInstall 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
○ The author declares no dsh version requirement — install is not blocked by version.
| 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.2.11 | ✓ | ✓ | · | · | · |
| 0.2.10 | · | · | ✓ | · | · |
| 0.2.9 | · | · | · | · | · |
| 0.2.8 | · | · | · | ✓ | ✓ |
| 0.2.4 | · | · | · | · | · |
0.2.11npm✓ 2 runtime-verified2026-11-05
@dsh-plugins/dsh-env-inspector
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.11
ID: dsh-env-inspector@0.2.11@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-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.
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.11
ID: dsh-env-inspector@0.2.11@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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.2.10npm✓ 1 runtime-verified2026-10-27
@dsh-plugins/dsh-env-inspector
✓dsh 0.2.1-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.10
ID: dsh-env-inspector@0.2.10@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.2.9npm2026-10-21
@dsh-plugins/dsh-env-inspector
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.2.8npm✓ 2 runtime-verified2026-10-18
@dsh-plugins/dsh-env-inspector
✓dsh 0.2.1-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.8
ID: dsh-env-inspector@0.2.8@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.8
ID: dsh-env-inspector@0.2.8@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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.2.4npm✓ 4 runtime-verified2026-10-10
@dsh-plugins/dsh-env-inspector
✓dsh 0.2.1-alpha.22026-10-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.4
ID: dsh-env-inspector@0.2.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-plugins/dsh-env-inspector@0.2.4
ID: dsh-env-inspector@0.2.4@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.
✓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-plugins/dsh-env-inspector@0.2.4
ID: dsh-env-inspector@0.2.4@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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @dsh-plugins/dsh-env-inspector@0.2.4
ID: dsh-env-inspector@0.2.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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-env-inspector/?ref=badge)``[](https://www.dsh.so/artifact/dsh-env-inspector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-env-inspector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-env-inspector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-env-inspector/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-env-inspector/?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.11dsh manifest0.2.11npm2026-11-050.2.11same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
lib/index.js:40const result = spawnSync(cmd, args, { - warningchildProcess · code-exec
lib/index.js:175const r = spawnSync(spPath, ['-json', 'SPDisplaysDataType', 'SPHardwareDataType'], { - warningchildProcess · code-exec
lib/index.js:441const result = spawnSync(cmd, ['-iTCP', '-sTCP:LISTEN', '-n', '-P'], { - warningshellExec · shell
lib/index.js:65execFile(cmd, args, { - warningshellExec · shell
lib/index.js:234execFile(spPath, ['-json', 'SPDisplaysDataType', 'SPHardwareDataType'], { - warningshellExec · shell
lib/index.js:465execFile(cmd, ['-iTCP', '-sTCP:LISTEN', '-n', '-P'], {
show 3 audit findings
- mediumkill-port route has no auth and fails open when Sec-Fetch-Site is absent, letting any caller SIGKILL a listening process
lib/index.js:685The only gate on the mutating route returns true whenever the Sec-Fetch-Site header is missing (curl, any local process, older clients) and also accepts 'same-origin', which a DNS-rebinding page satisfies. Such a caller can POST {port,pid} and reach process.kill(id,'SIGTERM') then 'SIGKILL' (lib/index.js:654-668). Only process.pid and ports 3080/19387 are protected, so any other user-owned listener (databases, IDE/dev servers, editors) can be killed while DSH is running, causing data loss. No token or session check exists.
- mediumUnauthenticated self-check route returns hostname, username, home path, LAN IPs and listening ports with PIDs
lib/index.js:610Same fail-open origin gate as the kill route, so any local process (or a rebinding page) can read the payload built from readSystem() (hostname, USER, HOME, shell) plus every listening port with command and PID, LAN interface addresses and the installed-plugin list. This is exactly the reconnaissance needed to drive the kill-port route, and the client persists the whole report in localStorage under 'dsh_env_inspector_store_v1', where any other bundle in the DSH web origin can read it.
- lowClient contacts third-party api.ipify.org to resolve public egress IP (user-initiated)
lib/client.jsA plugin advertised as '零联网 / 默认不联网' performs a request to a third-party service, disclosing the user's public IP and the fact that DSH is in use to api.ipify.org. It is behind an explicit button and labelled in the UI, and no report data is sent, so impact is limited to that third-party disclosure.
No RCE and no secret values read; subprocesses use fixed args. But two unauthenticated localhost routes (env report, kill-port) rely on a fail-open Sec-Fetch-Site check.
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-27 · activity: Active
• Repo created: 2026-09-22
• Stars: ★ 4 · 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 @webkubor/dsh-env-inspector?
@webkubor/dsh-env-inspector 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 @webkubor/dsh-env-inspector?
Run dsh plugin --profile web add @dsh-plugins/dsh-env-inspector 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-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.