🗑️ The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

@vi0let-dev/dsh-session-md-export

Export DeepSeek Harness (dsh) sessions as readable Markdown. Pick individual messages from one session, or merge several into a single .md / split them into a ZIP.

Ecosystem appKnowledgeStorageGitHub integration

Verification

L5 · Ecosystem app

Risk

Pending

Health

Active

Trust

Bronze

Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →

What it does

Export DeepSeek Harness (dsh) sessions as readable Markdown. Pick individual messages from one session, or merge several into a single .md / split them into a ZIP.

Installation

GitHub repository

Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).

The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.

Verification & Compatibility◼ Ecosystem app

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

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

◼ Ecosystem app

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4
3049f0	◼	◼

Install compatibility (by plugin version, dsh versions within)

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

3049f0github◼ 2 ecosystem app2026-10-19

https://github.com/vi0let-dev/dsh-session-md-export

◼dsh 0.2.1-rc.2current2026-10-19Ecosystem app

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/vi0let-dev/dsh-session-md-export (version unstated)

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

Unknown

L5 runtime

Not tested

Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)

Ecosystem app

ID: dsh-session-md-export@3049f0@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-19 · expires: 2026-10-26

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested? Unknown

Sandbox install verdictL4_0_SANDBOX? Unknown

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

spec github:vi0let-dev/dsh-session-md-export · channel GitHub source · outcome unknown

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.

◼dsh 0.2.1-alpha.42026-10-18Ecosystem app

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: github · https://github.com/vi0let-dev/dsh-session-md-export (version unstated)

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

Unknown

L5 runtime

Not tested

Ecosystem app

ID: dsh-session-md-export@3049f0@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

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

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

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

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

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

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

L4 · Install tested? Unknown

Sandbox install verdictL4_0_SANDBOX? Unknown

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

spec github:vi0let-dev/dsh-session-md-export · channel GitHub source · outcome unknown

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.

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-session-md-exportAutomated review · daily

Static n/a, dynamic no conclusion — stricter wins → overall low.

no static verdict→dynamic no conclusion→overall low

0 critical·— files scanned

lowoverall · low

1static scandeterministic rules · no code execution · shape only

Version binding

plugin version—

scanned version—

current version7d29e7e06a6d

The scan result is valid for the scanned commit. New commits within 7 days are tolerated (the rating still counts); after 7 days without a rescan the badge shows outdated.

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

not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

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

• Repo created: 2026-10-16

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/vi0let-dev/dsh-session-md-export

Plugin notes

What is @vi0let-dev/dsh-session-md-export?

@vi0let-dev/dsh-session-md-export is an ecosystem app maintained by @vi0let-dev, not a DSH plugin package — it cannot be installed via dsh plugin add; desktop / web shells ship through the project's own release channel. It is cataloged on dsh.so as a Knowledge entry, with a public source repository and automated static security scan.

How do I install @vi0let-dev/dsh-session-md-export?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. Its level reads L5 · Ecosystem app; 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 (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, and its conclusion can only raise the combined verdict, never exempt it. 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-16

@vi0let-dev/dsh-session-md-export

What it does

Installation

Verification & Compatibility◼ Ecosystem app

Author badges

Security Report

Activity

Source

Author README