⚠️ This repository has been renamed: cordisplugins/dsh-cordis — click to visit the new location. Everything below is preserved as originally indexed.

dsh-cordis

PluginDeveloperCode reviewMemory

Verification

L4 · Install tested

stale

Risk

Out of scope

Health

Stable

Trust

Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.0-rc.1 · last checked 09-30Install verification details →

What it doesAI

Packages the DeepSeek Harness coding engine as a Cordis plugin, mounting DSH agents, sessions and tools into an existing Loader tree.

Mounts the DSH base composition into a host's existing Loader tree
Provides native agents, durable sessions, model adapters and tools
Its Fiber owns the DSH tree, so disabling the entry removes live services

developerAIcode-reviewAImemoryAI

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 dsh-cordis@0.1.5

security scan passed · npm package v0.1.5

Install method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.0-rc.1

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

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

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.0-rc.1	dsh 0.1.7-rc.1
0.1.5	✗	·
v0.1.5	◐	·

Install compatibility (by plugin version, dsh versions within)

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

0.1.5npm1 failed2026-10-08

dsh-cordis

✗dsh 0.2.0-rc.12026-09-30L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.0-rc.1
• Plugin artifact: npm · dsh-cordis@0.1.5

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

Failed

Sandbox install failed

L5 · failed

ID: dsh-cordis@0.1.5@dsh0.2.0-rc.1 · profile: l5-web-smoke

Issued: 2026-09-30 · expires: 2026-12-29

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-cordis@0.1.5@dsh0.2.0-rc.2 (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-cordis@0.1.5@dsh0.2.0-rc.2 (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-cordis@0.1.5@dsh0.2.0-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec dsh-cordis · channel npm package · install mode reused L4 scratch

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec dsh-cordis · channel npm package · install mode reused L4 scratch

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec dsh-cordis · channel npm package · install mode reused L4 scratch

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec dsh-cordis · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

boot failed

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.1.5github◐ 1 testing2026-09-30

https://github.com/acryldev/dsh-cordis

◐dsh 0.2.0-rc.12026-09-30L4 · testing (install passed, runtime untested)

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.0-rc.1
• Plugin artifact: github · https://github.com/acryldev/dsh-cordis#v0.1.5

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

Not tested

Sandbox install passed (L4) — installs; runtime smoke (L5) untested, unknown whether it runs

L4 · testing (install passed, runtime untested)

ID: dsh-cordis@v0.1.5@dsh0.2.0-rc.1 · profile: l4-sandbox

Issued: 2026-09-30 · expires: 2026-10-07

View checks & evidence

L1 · Found✓ Passed

↳ carried from earlier record dsh-cordis@0.1.5@dsh0.2.0-rc.2 (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-cordis@0.1.5@dsh0.2.0-rc.2 (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-cordis@0.1.5@dsh0.2.0-rc.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec github:acryldev/dsh-cordis#v0.1.5 · channel GitHub source · outcome ran · exit 0

check took: 117.0s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec github:acryldev/dsh-cordis#v0.1.5 · channel GitHub source · outcome ran · exit 0

check took: 117.0s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec github:acryldev/dsh-cordis#v0.1.5 · channel GitHub source · outcome ran · exit 0

check took: 117.0s

Resolved version recordedL4.4_RESOLVED_ARTIFACT✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-30

spec github:acryldev/dsh-cordis#v0.1.5 · channel GitHub source · outcome ran · exit 0

check took: 117.0s

L5 · Run tested– Not tested

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.

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-cordisAutomated 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 versionv0.1.5dsh manifest

scanned version0.1.5npm2026-10-08

current version0.1.5same version

vet verdictclean · npm

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

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-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.

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-09 · activity: Stable

• Repo created: 2026-09-08

• Stars: ★ 1 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/acryldev/dsh-cordis

Plugin notes

What is the dsh-cordis DeepSeek Harness plugin?

dsh-cordis is a DeepSeek Harness plugin maintained by @acryldev. It is cataloged on dsh.so as a Developer plugin for Code review tasks, 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 dsh-cordis?

Run dsh plugin --profile web add dsh-cordis@0.1.5 in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4).

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/vet fused verdict 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-09-26

dsh-cordis

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README