Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · 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
Overleaf-style paper revision workbench with LaTeX support, powered by DeepSeek Harness plugin.
- Overleaf-style paper revision workbench
- LaTeX support for paper writing
- Integrated as DeepSeek Harness plugin
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 dsh-paperlabInstall method: npm · 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.
current (registry 2026-11-17) · 8 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-03 · 8 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
09-23 → 11-03 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-13 → 11-14 · 56 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
09-13 → 11-16 · 57 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 5 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×5
✗ Running dsh 0.2.2-rc.3 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 paperlab@0.1.2 0.2.2-rc.3 (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 |
|---|---|---|---|---|---|
| 0.1.2 | · | · | ✓ | ✓ | ✓ |
| v0.1.0 | · | · | · | · | · |
0.1.2npm✓ 10 runtime-verified2026-11-14
dsh-paperlab
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@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-paperlab@0.1.2
ID: paperlab@0.1.2@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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.1.7-rc.12026-09-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-paperlab@0.1.2
ID: paperlab@0.1.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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-paperlab@0.1.2
ID: paperlab@0.1.2@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.
v0.1.0github✓ 4 runtime-verified2026-09-11
https://github.com/maple-pwn/paperlab
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/maple-pwn/paperlab#v0.1.0
ID: paperlab@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-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.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/maple-pwn/paperlab#v0.1.0
ID: paperlab@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/maple-pwn/paperlab#v0.1.0
ID: paperlab@v0.1.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/maple-pwn/paperlab#v0.1.0
ID: paperlab@v0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-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.
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/paperlab/?ref=badge)``[](https://www.dsh.so/artifact/paperlab/?ref=badge-install)``[](https://www.dsh.so/artifact/paperlab/?ref=badge-install)``[](https://www.dsh.so/artifact/paperlab/?ref=badge-install)``[](https://www.dsh.so/artifact/paperlab/?ref=badge-install)``[](https://www.dsh.so/artifact/paperlab/?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 high (authoritative when present) → overall high.
v0.1.2dsh manifest0.1.2npm2026-11-170.1.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalnewFunction · code-exec
lib/index.js:233schema.callback = new Function("return " + schema.callback)(); - warningchildProcessImport · code-exec
lib/index.js:801import { execFile } from "child_process"; - warningnetIp · network
lib/index.js:1174const parsed = new URL(url, "http://127.0.0.1"); - warningnetIp · network
lib/index.js:1247options.onLog("info", `HTTP \u89E6\u53D1\u7AEF\u70B9\u5DF2\u5C31\u7EEA\uFF1Ahttp://127.0.0.1:${options.port}/api/revisions`); - warningfsWrite · files
lib/index.js:864await fs.writeFile(file, JSON.stringify(value, null, 2), "utf8"); - warningfsWrite · files
lib/index.js:932await fs.writeFile(abs, next, "utf8");
show 4 audit findings
- highUnauthenticated loopback /api/revisions starts a DSH agent on an attacker-supplied projectDir and instruction
lib/index.js:1210The endpoint has no token, Origin or Host check, and the body is parsed regardless of Content-Type, so any local process and any web page the user visits can start a revision. The body supplies an arbitrary absolute projectDir (validateProjectDir only stats it) and a free-form instruction that is concatenated into the agent's user message ('- 作者额外要求:${extra2}'), i.e. attacker text is injected into an LLM session that runs with cwd set to the chosen directory, runs 'git add -A'/'git commit' there and can rewrite any .tex/.bib/.sty/.cls/.bst/.bbl file under it while reading source content out to
- mediumlatexmk is run with cwd = project directory, so a project-supplied latexmkrc (Perl) is executed
lib/index.js:1015latexmk loads latexmkrc from its current directory and evaluates it as Perl. Because the audited directory is attacker-selectable through the unauthenticated /api/revisions endpoint (and its latexmkrc presence is explicitly detected to change engine flags), dropping a malicious latexmkrc into that directory yields arbitrary code execution as the user when the agent runs paperlab_compile_check. execFile itself is shell-free, so this is the actual code-execution path.
- mediumSymlink escape: containment check uses path.resolve without realpath, so a linked .tex reads/writes outside the project
lib/index.js:904assertInside only validates the lexical path; fs.realpath is never called. A file named e.g. 'leak.tex' that is a symlink to /etc/shadow or ~/.ssh/id_rsa passes the suffix and prefix checks, so paperlab_read_state reads it and returns its content to the model provider, and paperlab_apply_edits writes through the link and mutates a file outside the project root. Reachable whenever the audited directory contains such a symlink (cloned archives, or a link the agent itself creates).
- lowPOST /api/settings/model persists a new default provider/model without authentication
lib/index.js:1183The same unauthenticated surface lets any local process or web page call ctx.agentDefaultModel.saveSelection with arbitrary provider/model/reasoningEffort strings, persistently changing the harness default and the model that subsequent revision sessions use. Impact is limited to already-registered providers, so exploitation is more nuisance/denial than exfiltration, but it is a silent, persistent configuration change.
Unauthenticated loopback HTTP trigger starts a DSH agent on an attacker-supplied projectDir and instruction; compile check executes project latexmkrc and path checks miss symlinks.
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-15 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 10 · Forks: 1
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/maple-pwn/paperlab
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 paperlab?
paperlab 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 paperlab?
Run dsh plugin --profile web add dsh-paperlab 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-17 (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.
