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
PaperForge lets you annotate papers in DSH: highlight selections, ask questions in per-paper sessions, and capture screenshot notes with backlinks.
- Highlight selected text in papers inside DSH
- Ask selected text questions in dedicated per-paper sessions
- Marquee-capture screenshots into notes with backlinks
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:PhysicalAI-0/dsh-paperforge#v1.0.0Install method: GitHub · sandbox install ok, web smoke failed (L5)
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), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-05 → 11-08 · 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-11 → 11-08 · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.0.0 | ✗ | ✓ | ✓ | ✓ | ✓ |
v1.0.0github✓ 8 runtime-verified1 failed2026-11-14
https://github.com/PhysicalAI-0/dsh-paperforge
✗dsh 0.2.2-rc.3current2026-11-14L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · github:PhysicalAI-0/dsh-paperforge#v1.0.0#v1.0.0
ID: dsh-paperforge@v1.0.0@dsh0.2.2-rc.1 · profile: l5-web-smoke
Issued: 2026-11-06 · expires: 2027-02-04
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: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@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.
✓dsh 0.2.1-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@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.
✓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/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@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.42026-10-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@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: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/PhysicalAI-0/dsh-paperforge#v1.0.0
ID: dsh-paperforge@v1.0.0@dshunknown · profile: l3-fullscan
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.
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-paperforge/?ref=badge)``[](https://www.dsh.so/artifact/dsh-paperforge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-paperforge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-paperforge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-paperforge/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-paperforge/?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.
v1.0.0dsh manifestv1.0.0git2026-11-14v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalnewFunction · code-exec
verify.mjs:355new Function("window", "document", "navigator", "fetch", "getComputedStyle", "console", source)( - warningshellExec · shell
lib/index.js:171execFile( - warningnetIp · network
verify.mjs:101new Request("http://127.0.0.1/api/paper.log", { - warningnetIp · network
verify.mjs:119new Request("http://127.0.0.1/api/paper.clip", { - warningnetIp · network
verify.mjs:167new Request(`http://127.0.0.1${path}`, { - warningfsWrite · files
verify.mjs:140fs.writeFileSync( - warningfsWrite · files
verify.mjs:216fs.writeFileSync(file, base); - warningfsWrite · files
verify.mjs:221fs.writeFileSync(file, `${mine}\n> 插件追加\n`);
show 3 audit findings
- mediumPython interpreter is resolved from workspace-local paths and then executed
lib/index.js:90resolvePython() puts two workspace-relative candidates ahead of the PATH fallbacks, and the chosen path is handed to execFile at lib/index.js:171 (runPython). A workspace that ships a planted ".pixi/envs/default/bin/python" (or, if the bundled script is absent, "tools/paper_clip.py" via resolveClipScript at line 70) gets that executable run with plugin-chosen arguments as soon as the highlight-to-PDF path is used (POST /api/paper.clip with mode:'highlight' and writePdf:true). There is no shell, so this is not command injection from the request body, but the binary itself originates from worksp
- lowHealth endpoint discloses absolute host paths, note folders and client log tail
lib/index.js:455handleHealth (no request validation beyond JSON parsing) returns workspaceRoot, every DSH workspace root, the resolved interpreter/script paths, note-folder names and the last 12 lines of .paper-log to any caller that can POST /api/paper.health. The exporter performs no caller/origin check itself, so the endpoint is an unadvertised host-layout disclosure surface for anything that can reach the DSH web port.
- lowCaller-supplied text is appended to workspace files that a later agent turn reads
lib/index.js:410handleDiag (and handleLog at line 475) append up to 2 KB / 4 KB of caller-controlled text into <workspace>/paperforge_notes/_diag/_diag.md and <workspace>/paperforge_notes/.paper-log with no origin or authentication check in the handler. The plugin's own design states these files are the 'browser -> agent' observation channel, so a caller that can reach the port can plant arbitrary Markdown (including instructions) in files an agent session is expected to read, i.e. an indirect prompt-injection channel into a later agent turn.
Host half writes notes and runs a Python sidecar via argv-array execFile (no shell); path guards hold, but the interpreter is resolved from workspace-local paths, so a hostile workspace can supply it.
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-29 · activity: Stable
• Repo created: 2026-09-29
• Stars: ★ 3 · 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 @PhysicalAI-0/dsh-paperforge?
@PhysicalAI-0/dsh-paperforge 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 @PhysicalAI-0/dsh-paperforge?
Run dsh plugin --profile web add github:PhysicalAI-0/dsh-paperforge#v1.0.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-11-14 (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.