Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Local-first DSH artifact vault that auto-collects AI outputs, AI-organizes and semantically searches them, plus a bundled-Everything file manager.
- Auto-collects AI deliverables across sessions into a local vault
- AI classification, semantic one-sentence search and suggested linking
- Bundled Everything engine for local file search and directory browsing
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:wyq183/dsh-artifact-library#v0.4.1Install method: GitHub · sandbox install ok, web smoke failed (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 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| v0.4.1 | ✗ | ✗ | · |
| v0.3.4 | · | · | ✗ |
v0.4.1github2 failed2026-10-19
https://github.com/wyq183/dsh-artifact-library
✗dsh 0.2.1-rc.2current2026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wyq183/dsh-artifact-library#v0.4.1
ID: dsh-artifact-library@v0.4.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wyq183/dsh-artifact-library#v0.4.1
ID: dsh-artifact-library@v0.4.1@dsh0.2.1-alpha.4 · profile: l3-fullscan
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.3.4github1 failed2026-10-21
https://github.com/wyq183/dsh-artifact-library
✗dsh 0.2.1-alpha.22026-10-14L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/wyq183/dsh-artifact-library#v0.3.4
ID: dsh-artifact-library@v0.3.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-artifact-library@v0.3.4@dsh0.2.1-rc.2 (l3-fullscan)
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-artifact-library/)`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 — stricter wins → overall medium.
v0.4.1dsh manifestv0.4.1git2026-10-21v0.4.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningfsWrite · files
lib/cleanup.js:25fs.writeFileSync(file, JSON.stringify(store.exportData(), null, 2), 'utf8') - warningchildProcess · code-exec
lib/http.js:200const p = spawn('explorer.exe', ['/select,' + rec.path], { windowsVerbatimArguments: true, detached: true, stdio: 'ignore' }) - warningfsWrite · files
lib/store.js:122fs.writeFileSync(this.metaFile, JSON.stringify(this.meta, null, 2), 'utf8') - warningfsWrite · files
lib/store.js:222fs.writeFileSync(tmp, JSON.stringify(this.items, null, 2), 'utf8')
show 3 audit findings
- mediumBodyless state-changing POST endpoints lack CSRF/Origin protection
lib/http.js:118cleanup-now (and :id/open, :id/trash, :id/restore) are POST handlers that never read a request body and never check Origin/Referer. A malicious web page the user visits can submit a simple cross-site form POST to http://127.0.0.1:PORT/ext/artifacts/cleanup-now; the browser socket is 127.0.0.1, so isLoopback treats it as local and cleanup runs (archives duplicate records, rewrites artifacts.json, writes backups) without user intent.
- lowNon-loopback clients can enumerate artifact metadata including absolute file paths
lib/http.js:56With webServer bound to 0.0.0.0, LAN clients may GET /ext/artifacts (store.list) and /ext/artifacts/suggest-cleanup, both of which return full absolute filesystem paths plus settings, disclosing usernames and directory layout even though file content stays protected.
- lowisLoopback fails open when socket.remoteAddress is absent
lib/http.js:28Any request that reaches the handler without a resolvable peer address (unusual proxy/mock setups) is treated as local and gains full read/write and file-content access, inverting the intended security boundary.
Loopback gate protects file content and writes, but bodyless POST actions (cleanup-now) lack CSRF/Origin checks and LAN clients can read absolute paths.
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-20 · activity: Active
• Repo created: 2026-08-14
• 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).
