@waning-sun/dsh-napcat-keeper

在DSH运行时自动运行napcat的小插件

Plugin

Verification

L5 · Run tested

Verified

Risk

LowRisk

Health

Active

Trust

Gold

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked 10-28Install verification details →

What it does

在DSH运行时自动运行napcat的小插件

Installation

dsh plugin --profile web add dsh-napcat-keeper

verified 2.8.2

Install method: npm · runtime verified (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

Declared DSH compatibilityfrom package.json · peerDependencies

package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.3 current
2.8.2	✓

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

2.8.2npm✓ 1 runtime-verified2026-10-28

dsh-napcat-keeper

✓dsh 0.2.1-rc.3current2026-10-28L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.3
• Plugin artifact: npm · dsh-napcat-keeper@2.8.2

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Passed

Install + runtime smoke verified in the dsh sandbox — installs and runs

L5 · runtime verified · valid for dsh 0.2.1-rc.3

ID: dsh-napcat-keeper@2.8.2@dsh0.2.1-rc.3 · profile: l4-sandbox

Issued: 2026-10-28 · expires: 2026-11-04

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-napcat-keeper@ff77ac@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

↳ carried from earlier record dsh-napcat-keeper@ff77ac@dsh0.2.1-rc.3 (l3-fullscan)

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

↳ carried from earlier record dsh-napcat-keeper@ff77ac@dsh0.2.1-rc.3 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-28

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-28

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-28

spec dsh-napcat-keeper · channel npm package · outcome ran · exit 0

check took: 3.3s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-28

spec dsh-napcat-keeper · channel npm package · outcome ran · exit 0

check took: 3.3s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-28

spec dsh-napcat-keeper · channel npm package · outcome ran · exit 0

check took: 3.3s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-28

spec dsh-napcat-keeper · install mode reused L4 scratch

check took: 110ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-28

ready line dsh web: http://127.0.0.1:49813/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-28

path / · HTTP 200 · took 110ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-28

verdict active · entries 150

match: include:napcat-keeper · dsh-napcat-keeper · phase active

phases: active 122 · null 28

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per 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:

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-napcat-keeperAutomated 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 versionv2.8.2dsh manifest

scanned version2.8.2npm2026-10-28

current version2.8.2same version

vet verdictclean · npm

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

show static findings (11)

warningchildProcess · code-execlib/index.js:912
child = spawn(file, args, { windowsHide: true, stdio: ['ignore', 'pipe', 'ignore'] })
warningchildProcess · code-execlib/index.js:2941
const child = spawn('explorer.exe', [hasCmd ? `/select,${p.cmd}` : p.dir], {
warningchildProcess · code-execlib/index.js:3060
const child = spawn('cscript.exe', ['//nologo', vbsFile], {
warningshellExec · shelllib/index.js:499
execFileSync(file, args, {
warningshellExec · shelllib/index.js:1829
execFileSync('schtasks.exe', ['/query', '/tn', cfg.taskName], {
warningshellExec · shelllib/index.js:2215
execFileSync(
warningnetIp · networklib/index.js:1295
const BRIDGE_DEFAULTS = { napcat: 'http://127.0.0.1:3000', enabled: false, dryRun: true }
warningbase64Decode · obfuscationlib/index.js:2675
$bytes = [Convert]::FromBase64String($s.contentBase64)
warningnewFunction · code-execscripts/smoke-client.mjs:29
new Function('window', 'fetch', code)(globalThis.window, globalThis.fetch);
warningnetIp · networkscripts/smoke-client.mjs:191
napcatUrl: 'http://127.0.0.1:8643',
warningnetIp · networkscripts/smoke-client.mjs:197
note: 'dsh-qq-bridge 连的是 http://127.0.0.1:8643，而那个端口现在是反向 WebSocket',

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

• Repo created: 2026-10-26

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/waning-sun/dsh-napcat-keeper

Plugin notes

What is the @waning-sun/dsh-napcat-keeper DeepSeek Harness plugin?

@waning-sun/dsh-napcat-keeper is a DeepSeek Harness plugin maintained by @waning-sun. It is cataloged on dsh.so as a Developer plugin, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install @waning-sun/dsh-napcat-keeper?

Run dsh plugin --profile web add dsh-napcat-keeper in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4) plus web smoke testing (L5).

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static scan verdict (vet primary, dsh backstop) applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-27

@waning-sun/dsh-napcat-keeper

What it does

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README