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
Read-only checker comparing npm and GitHub versions, notifying updates in-app, and flagging breaking changes in release notes.
- Compares versions across npm and GitHub
- In-app update notification
- Annotates breaking changes in release notes
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.
5 samples (roughly every 7 days), 1 of them reconstructed (hollow dots); sampled points, not a daily series
10-01 → 11-01 · 5 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-11 → 11-01 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:1207627875/dsh-update-lens#v1.0.3Install method: GitHub · 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 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v1.0.3 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v1.0.0 | · | · | · | · | · |
v1.0.3github✓ 8 runtime-verified2026-11-05
https://github.com/1207627875/dsh-update-lens
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@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-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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: github · https://github.com/1207627875/dsh-update-lens#v1.0.3
ID: dsh-update-lens@v1.0.3@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.
v1.0.0github✓ 2 runtime-verified2026-09-25
https://github.com/1207627875/dsh-update-lens
✓dsh 0.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.0
ID: dsh-update-lens@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/1207627875/dsh-update-lens#v1.0.0
ID: dsh-update-lens@v1.0.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
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-update-lens/?ref=badge)``[](https://www.dsh.so/artifact/dsh-update-lens/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-update-lens/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-update-lens/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-update-lens/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-update-lens/?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 low (authoritative when present) → overall low.
—v1.0.3git2026-11-05v1.0.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalshellExec · shell
research/diagnose-github-access.mjs:13const require = createRequire(join(execSync('npm root -g', { encoding: 'utf8' }).trim(), '@deepseek-ai/dsh', 'lib', 'bin.js')); - warningnetIp · network
client.js:755placeholder: 'http://127.0.0.1:7890', - warningnetIp · network
index.js:954resolvePort({ port, url: `http://127.0.0.1:${port}`, listening }); - warningnetIp · network
research/diagnose-github-access.mjs:10const PROXY = 'http://127.0.0.1:7890'; - warningshellExec · shell
research/repair-encoding.mjs:212execFileSync(process.execPath, ['--check', file(name).pathname.replace(/^\//, '')], { stdio: 'pipe' }); - warningshellExec · shell
research/verify-remote.mjs:33return execFileSync(bin, ['auth', 'token'], { encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] }).trim(); - warningshellExec · shell
research/verify-remote.mjs:77execFileSync('tar', ['-xzf', 'repo.tgz'], { cwd: WORK, stdio: 'pipe' }); - warningshellExec · shell
research/verify-remote.mjs:91const scan = execFileSync(process.execPath, [scanner, ...scannerArgs], { cwd: unpacked, encoding: 'utf8' });
show 3 audit findings
- lowGET routes (/proxy-probe, /status) skip the same-origin guard applied to every mutating route; /proxy-probe sweeps local ports
index.js:1051Any party able to reach the local web server can trigger probeLocalPorts() (TCP connect to 11 well-known localhost ports) with a plain GET; GET /status likewise returns config (proxyUrl, githubApiBase) and the absolute DSH_HOME path without the guard. No CORS header is set, so a cross-site page cannot read the response body; the residual impact is unsolicited local probing and a CSRF-triggerable read path.
- lowsameOrigin compares the Origin host to the client-supplied Host header only, so it is not rebinding-proof
index.js:904Both compared values come from the request itself, and there is no loopback-name allowlist. A page whose hostname is rebound to 127.0.0.1 on the same port (or any local/raw client) can pass the check and POST /config, redirecting proxyUrl or githubApiBase so later update checks traverse attacker-controlled infrastructure and show attacker-authored release notes. No secret, token or command result crosses that channel, so the realistic impact is misleading update information.
- lowResearch-only scripts run shell commands and execute a scanner downloaded from the network; never imported by the runtime
research/diagnose-github-access.mjs:13These are developer diagnostics executed by hand, not plugin code: cordis.patch.yml mounts only dsh-update-lens and index.js/client.js/notes.js never import research/. When a maintainer does run verify-remote.mjs, it downloads a repository tarball and executes the scanner found inside it, so a compromised upstream repository would run code on the maintainer's machine. Not reachable from plugin load, routes or any user input; the execSync argument is a fixed literal with no interpolation.
Runtime halves only read public version data over HTTPS and write their own config; no shell/eval/auto-update, and the static scan's shell hits live in research tooling the runtime never loads.
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-27 · activity: Stable
• Repo created: 2026-09-21
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 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 @1207627875/dsh-update-lens?
@1207627875/dsh-update-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 @1207627875/dsh-update-lens?
Run dsh plugin --profile web add github:1207627875/dsh-update-lens#v1.0.3 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.