dsh.so
EN
English中文
@liutingqiu/dsh-purge avatar

@liutingqiu/dsh-purge

Independent community build of dsh-purge 1.1.77 for DSH 0.2.1 — restored 23 redteam skills + exact-host own-server allowlist. Upstream: YuJunZhiXue/dsh-purge.

PluginKnowledgeNetwork
Verification
L3 · Install spec
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: No L4/L5 install test yetInstall verification details →

What it does

Independent community build of dsh-purge 1.1.77 for DSH 0.2.1 — restored 23 redteam skills + exact-host own-server allowlist. Upstream: YuJunZhiXue/dsh-purge.

Installation

dsh plugin --profile web add github:liutingqiu/dsh-purge
verified

Install method: GitHub · install spec verified (L3)

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

Declared DSH compatibilityfrom package.json · peerDependencies
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v1.1.77-full.1github2026-10-28

https://github.com/liutingqiu/dsh-purge

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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:

dsh.so risk
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-purge-9.svg)](https://www.dsh.so/artifact/dsh-purge-9/)`

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.

dsh-purge-9Automated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low
vet findings0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
Version binding
plugin versionv1.1.77dsh manifest
scanned versionv1.1.77-full.1git2026-10-28
current versionv1.1.77-full.1same version
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (5)
  • warningfsWrite · fileslib/mnemon-settings.js:32

    fs.writeFileSync(fd, content, encoding);

  • warningchildProcess · code-execlib/uninstall-restart.js:65

    const child = spawn(info.execPath, info.argv, {

  • warningmanifest-fs-unfenced · sandboxpresets/redteam/agent.cordis.yml

    Mutating filesystem tool has no explicit fs backend in realm

  • warningmanifest-search-unfenced · sandboxpresets/redteam/agent.cordis.yml

    Search tool reads without an explicit fs mount

  • warningmanifest-shell-unfenced · sandboxpresets/redteam/agent.cordis.yml

    Shell tool without a sandbox runner or policy in realm

2dynamic auditmodel reads redacted source context · never executes plugin code

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

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-10-26 · activity: Active

• Repo created: 2026-10-26

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/liutingqiu/dsh-purge

Was this page helpful?