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 →
Data as of (UTC)
What it doesAI
Self-diagnosing, self-repairing, self-iterating dynamic plugin for DSH that keeps itself healthy and evolving.
- Self-diagnoses its own state and problems
- Self-repairs automatically when issues are found
- Self-iterates to keep the plugin evolving
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:ckk-09/dsh-refixInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.1-rc.3
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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| ea55ea | · | · | · | · | · |
| 310d66 | ○ | ○ | ○ | ○ | ○ |
ea55ealocal2026-09-16
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
310d66github○ 11 ecosystem plugin2026-10-30
https://github.com/ckk-09/dsh-refix
○dsh 0.2.1-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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-rc.22026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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.6-alpha.12026-09-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dsh0.1.6-alpha.1 · profile: l3-fullscan
Issued: 2026-09-18 · expires: 2026-09-25
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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: github · https://github.com/ckk-09/dsh-refix (version unstated)
ID: dsh-refix@310d66@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-refix@310d66@dsh0.2.1-rc.5 (l3-fullscan)
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.
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/dsh-refix/?ref=badge)`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 low (authoritative when present) → overall low.
—13bd4cc2e0ccgit2026-10-3013bd4cc2e0ccsame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalnewFunction · code-exec
ac/pre3-smoke.mjs:49const factory = new Function('harness', src(file)) - criticalnewFunction · code-exec
ac/pre3-smoke.mjs:69const factory = new Function('harness', src(file)) - warningchildProcess · code-exec
deploy/static/dump-config-check.mjs:31const result = spawnSync(DSH_CMD, ['--profile', PROFILE, '--dump-config'], {
show 2 audit findings
- lowAcceptance script evaluates repo version files with new Function
ac/pre3-smoke.mjs:49The script reads versions/*.js from the repository and compiles/executes them with full Node privileges. Whoever can write a version file (or point the script at another file) gets arbitrary code execution in that process. The input is a hard-coded repo path, not remote data, and this file is a manual acceptance harness that the plugin runtime does not load, so no untrusted input reaches it.
- lowDeploy probe spawns dsh through a shell using CLI-supplied arguments
deploy/static/dump-config-check.mjs:31With shell:true the value passed via --profile (and --dsh/--ids) is interpolated into a shell command line, so shell metacharacters in an operator-supplied profile name are interpreted rather than passed literally; the same script writes the full dumped config (which may contain profile settings) to the path given by --out via writeFileSync. Both are self-inflicted: the values come from whoever runs the deploy check locally, so there is no attacker-controlled path.
No critical or high runtime risk: the only risky constructs live in acceptance/deploy tooling and act on repo-local files or operator-supplied CLI args.
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-09-18 · activity: Stable
• Repo created: 2026-09-16
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/ckk-09/dsh-refix
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 dsh-refix?
dsh-refix is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 dsh-refix?
Run dsh plugin --profile web add github:ckk-09/dsh-refix in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-10-30 (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.