Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin for local file search, clickable path detection, and floating preview with EverythingCLI integration.
- Local file search
- Clickable path detection
- Floating preview with optional EverythingCLI
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:fastengiel-kurai/dsh-peekfile-everything#v0.1.0Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
6 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-03 · 6 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-01 → 11-03 · 5 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 6 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.8 ×6
✗ 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-peekfile-everything@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-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v0.1.0github16 failed2026-11-20
https://github.com/fastengiel-kurai/dsh-peekfile-everything
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
This level was not executed in this scan.
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-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
This level was not executed in this scan.
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-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@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-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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.7-alpha.22026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@v0.1.0@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: github · https://github.com/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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/fastengiel-kurai/dsh-peekfile-everything#v0.1.0
ID: dsh-peekfile-everything@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-peekfile-everything/?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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifestv0.1.0git2026-11-21v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalshellExec · shell
src/ebook.js:12const probe = async (command,args=['--version']) => { if(!command)return null;try { await exec(command,args,{timeout:5000,maxBuffer:1<<20}); - criticalshellExec · shell
src/ebook.js:44epub=join(output,'converted.epub');try{await access(epub)}catch{await exec(capability.converter,[source,epub],{timeout:180000,maxBuffer:16<< - criticalshellExec · shell
src/ebook.js:46try{await access(marker)}catch{await exec('unzip',['-oq',epub,'-d',output],{timeout:120000,maxBuffer:8<<20});await import('node:fs/promises' - criticalshellExec · shell
src/office.js:18try { await exec(command, ['--version'], { timeout:5000, maxBuffer:1<<20 }); return command } catch {} - criticalshellExec · shell
src/office.js:35try{await exec(officecli,['view',source,'html','-o',output],{timeout:180000,maxBuffer:32<<20});await access(output);return output}catch{} - criticalshellExec · shell
src/office.js:40try{await exec(anydoc,[source,'-o',output],{timeout:180000,maxBuffer:32<<20});await access(output);return output}catch{} - warningfsWrite · files
src/ebook.js:46try{await access(marker)}catch{await exec('unzip',['-oq',epub,'-d',output],{timeout:120000,maxBuffer:8<<20});await import('node:fs/promises'
show 3 audit findings
- mediumUntrusted previews render in same-origin, unsandboxed iframes so document scripts run with DSH origin privileges
src/client.jsThe plugin reads the preview iframe's contentDocument, so previews (raw HTML, EPUB chapters via frame.src=chapter.href in src/ebook.js, Office->HTML output, PDF renders) are loaded with the same origin as the DSH UI. Scripts embedded in an attacker-supplied document that the user previews can reach window.parent: read the page/draft text, call the local /__peekfile/api (path-driven read/preview endpoints) and insert text into the chat draft, turning 'open a file' into file access plus prompt injection into the agent.
- mediumThird-party OCR upload channel is enabled by default and ships a hardcoded token-file path
src/client.jsAfter install the OCR feature is already on and points at a remote service; screen captures (getDisplayMedia region grab) and full-page PDF rasters are uploaded out of the machine, and the host is expected to read whatever path sits in tools.mineru.tokenPath and send its contents as an auth header to tools.mineru.endpoint - a path outside the workspace that is fully user/UI controlled.
- lowPersonal absolute paths, including a secrets-file path, are hardcoded as plugin defaults
src/client.jsEvery installer inherits one developer's home/WSL layout and, notably, the path of a real credential file under a secrets directory. The defaults are persisted to localStorage and forwarded to the local host (x-peekfile-tools / api capability calls), so a machine that happens to have that path causes the host to open it; it also leaks the author's environment to the registry.
Converter calls use execFile without a shell, but previews render untrusted documents in same-origin unsandboxed iframes and MinerU upload is on by default with a hardcoded secret path.
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-28 · activity: Stable
• Repo created: 2026-08-19
• 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 dsh-peekfile-everything?
dsh-peekfile-everything 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-peekfile-everything?
Run dsh plugin --profile web add github:fastengiel-kurai/dsh-peekfile-everything#v0.1.0 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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-21 (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.
