Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH client plugin: select text in a conversation, write a note about it, and hand the model both the quote and your note.
Installation
dsh plugin --profile web add github:j7708git/dsh-quote-noteInstall 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| c4e62a | ✓ |
c4e62agithub✓ 1 runtime-verified2026-10-18
https://github.com/j7708git/dsh-quote-note
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/j7708git/dsh-quote-note (version unstated)
ID: dsh-quote-note@c4e62a@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-quote-note/)``[](https://www.dsh.so/artifact/dsh-quote-note/)`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 — stricter wins → overall low.
v0.4.0dsh manifest0.4.0git2026-10-210.4.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnewFunction · code-exec
tools/load-client.mjs:49const run = new Function("window", "document", source); - warningnetIp · network
tools/verify-client.mjs:111const res = await fetch(`http://127.0.0.1:${CDP_PORT}/json/version`); - warningnetIp · network
tools/verify-client.mjs:122const list = await (await fetch(`http://127.0.0.1:${CDP_PORT}/json/list`)).json(); - warningnetIp · network
tools/verify-m7.mjs:108const res = await fetch(`http://127.0.0.1:${CDP_PORT}/json/version`); - warningnetIp · network
tools/verify-m7.mjs:119const list = await (await fetch(`http://127.0.0.1:${CDP_PORT}/json/list`)).json();
show 3 audit findings
- lowDev-only test helper executes client.js source via new Function
tools/load-client.mjs:49Dynamic evaluation of a string. However the string is read from the plugin's own client.js (`readFileSync(CLIENT_PATH)`), the file lives in tools/ and is only imported by the test suite — DSH's loader never executes it. No untrusted input reaches `new Function`, so heuristically flagged code-exec is not reachable in the plugin runtime.
- lowOfficial module resolved and imported from env-derived anchor paths
index.js:51host-compat.resolveOfficial (host-compat.js:41 `return req.resolve(spec);`) resolves `@deepseek-ai/dsh-llm` through createRequire over anchors taken from DSH_PROFILE_DIR / DSH_HOME. The spec itself is hardcoded, and the anchors are the user's own DSH profile directories, so anyone able to plant a module there already runs code in the same process; the fallback path still builds a plain message object. No attacker-controlled specifier or path is accepted.
- lowPending quote store keyed only by client-supplied sessionId
index.js:80The GET/POST handler trusts the client's sessionId (validated only for type, length and control chars) and never checks it against the requesting connection, so any caller that can reach the authenticated route could read a count or overwrite/clear another session's pending items inside the same DSH instance — and those items are later injected into the model context. Exploitation requires authenticated access to the user's own local DSH instance, so impact is limited to self/same-user interference.
Host and client halves are coherent and validated; the only risky constructs are a dev-only `new Function` test harness, an env-anchored dynamic import of an official package, and session-unbound pending storage.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-07 · activity: Active
• Repo created: 2026-10-06
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 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).