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
Obsidian vault observation plugin for DSH: takes vault metadata snapshots, tracks edit stats, and shows an observation panel.
- Snapshots Obsidian vault metadata for the harness
- Tracks vault edit statistics over time
- Provides an observation panel inside DSH
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:chemmy-11/dsh-nautilusInstall 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 |
|---|---|---|---|
| 265415 | ✗ | ✗ | ✗ |
265415github3 failed2026-10-18
https://github.com/chemmy-11/dsh-nautilus
✗dsh 0.2.1-rc.2current2026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/chemmy-11/dsh-nautilus (version unstated)
ID: dsh-nautilus@265415@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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/chemmy-11/dsh-nautilus (version unstated)
ID: dsh-nautilus@265415@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-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/chemmy-11/dsh-nautilus (version unstated)
ID: dsh-nautilus@265415@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
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-nautilus/)`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.0.1dsh manifest0.0.1git2026-10-210.0.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalshellExec · shell
src/sqlite.ts:24exec(sql: string): void
show 1 audit findings
- lowInstall/build script executes tsc resolved from a heuristically auto-detected home directory
scripts/prepare.mjs:91prepare.mjs also runs as the npm/pnpm `prepare` script for git/tarball installs. detectCheckout() (line 40-49) accepts $DSH_CHECKOUT or silently probes $HOME/dsh-harness, $HOME/dsh and $HOME/.dsh/dsh-harness, then symlinks that tree's packages into node_modules and executes its typescript/bin/tsc via the current Node binary. Anyone able to plant such a directory in the developer's home would get a JS file executed during a later install/build of this package. Impact is limited: it needs local write access to the build machine's home and only yields code execution the attacker could already ach
Static-scan critical not reproducible: the only child_process use is in developer/build scripts, never loaded by the plugin runtime; no exfiltration or user-data abuse found in harvested code.
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-15 · activity: Active
• Repo created: 2026-08-24
• Stars: ★ 1 · 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).
