Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Startup safety wrapper for dsh: when a plugin breaks boot, it auto-disables the plugin in config and retries.
- Wraps dsh startup and detects failing plugin from errors
- Disables the bad plugin in profile patch yml and logs quarantine
- Automatically retries; supports update-and-start flow (u)
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 @hyzyn/dsh-safeInstall method: npm · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.18.1 | ○ | ○ | ○ | ○ | · |
| 0.18.0 | · | · | · | · | ○ |
| 0.17.0 | · | · | · | · | · |
| 0.16.0 | · | · | · | · | · |
| 0.16.0-rc.2 | · | · | · | · | · |
0.18.1npm○ 5 ecosystem plugin2026-10-20
@hyzyn/dsh-safe
○dsh 0.2.1-rc.2current2026-10-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.1
ID: dsh-safe-3@0.18.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.1
ID: dsh-safe-3@0.18.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.1
ID: dsh-safe-3@0.18.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.1
ID: dsh-safe-3@0.18.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.1
ID: dsh-safe-3@0.18.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.18.0npm○ 2 ecosystem plugin2026-10-01
@hyzyn/dsh-safe
○dsh 0.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.0
ID: dsh-safe-3@0.18.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.18.0
ID: dsh-safe-3@0.18.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.17.0npm○ 4 ecosystem plugin2026-09-25
@hyzyn/dsh-safe
○dsh 0.1.7-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.17.0
ID: dsh-safe-3@0.17.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
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-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.17.0
ID: dsh-safe-3@0.17.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.17.0
ID: dsh-safe-3@0.17.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.17.0
ID: dsh-safe-3@0.17.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.16.0npm○ 1 ecosystem plugin2026-09-17
@hyzyn/dsh-safe
○dsh 0.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @hyzyn/dsh-safe@0.16.0
ID: dsh-safe-3@0.16.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.16.0-rc.2npm2026-09-14
@hyzyn/dsh-safe
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem 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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-safe-3/)`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.18.10.18.1npm2026-10-210.18.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcessImport · code-exec
lib/ai.js:14import { spawnSync } from 'node:child_process' - warningchildProcess · code-exec
lib/dshpkg.js:31: spawn(bin, args, { encoding: 'utf8' }) - warningchildProcess · code-exec
lib/dshpkg.js:38: spawn(bin, args, { stdio: 'inherit' }) - warningchildProcess · code-exec
lib/verify.js:48const { status, stderr } = spawn(target.file, [...target.prefix, '--profile', 'verify'], { - warningchildProcess · code-exec
lib/wrap.js:63const child = spawn(target.file, [...target.prefix, ...(target.shell ? args.map(quoteShellArg) : args)], {
show 3 audit findings
- mediumWindows package-manager spawn uses shell:true while only the binary path is quoted; args are passed raw to cmd.exe
lib/dshpkg.js:30With shell:true Node joins `args` into a cmd.exe command line without escaping; quoteShellArg is applied only to `bin`. Any caller that forwards a package name, version or path containing cmd metacharacters (& | ^ %) gets command execution in the user's context. Callers live in lib/update.js and lib/repair.js, which were not provided, so reachability is unconfirmed; the in-file comment claims names/versions are validated (^[\w.+-]+$) but that guard is not visible in the audited code. Note that patch-row `name:` values are not constrained by this validator (unquote() in patchfile.js accepts arb
- lowOpt-in AI explain/detect sends raw stderr (only home path redacted) to a configurable remote endpoint
lib/ai.js:26The only sanitisation before `fetch(`${base}/chat/completions`)` is replacing the home directory. Startup stderr routinely contains plugin config values, tokens or internal paths, all of which leave the machine when DSH_SAFE_AI_KEY is set (or DSH_SAFE_AI_RECOVER=1 in the boot path). The feature is documented and opt-in, and model output is only ever used as hints matched against real patch rows, so this is a disclosure risk rather than an execution risk.
- lowManaged-block rewriting writes to file paths taken verbatim from the on-disk ledger
lib/quarantine.js:47quarantine.json is loaded and its per-entry `file` values are used as write targets after only readIfExists + managed-block append; there is no check that the path is a cordis.patch.yml under DSH_HOME. A tampered or corrupted ledger (same-user writable) redirects the write to any readable/writable file, appending dsh-safe managed-block text to it. Requires local write access to $DSH_HOME/dsh-safe, so impact is limited.
Quarantine logic is fail-closed and defensive, but Windows npm/pnpm spawning uses shell:true with unescaped args, and opt-in AI sends raw stderr off-box.
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-09-30 · activity: Active
• Repo created: 2026-09-05
• Stars: ★ 4 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/hyzyn/dsh-safe
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).