@hy-sde/dsh-logseq

Logseq for DeepSeek Harness: host-plane wiki-graph service (ctx.wikiGraph) over the Logseq CLI plus model-facing logseq_* tools — a headless alternative to the desktop MCP bridge.

Ecosystem pluginKnowledgeTerminalDesktopMemoryFileTerminal / Shell

Verification

L5 · Ecosystem plugin

Ecosystem plugin

Risk

LowRisk

Health

Active

Trust

Silver

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 →

What it doesAI

Hosts a Logseq wiki-graph service over the Logseq CLI and exposes model-facing logseq_* tools as a headless DSH alternative to the desktop MCP bridge.

Exposes a host-plane wiki-graph service via ctx.wikiGraph
Registers model-facing logseq_* tools for the harness
Headless replacement for the desktop MCP bridge

knowledgeAImemoryAIfileAI

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:hy-sde/dsh-logseq

verified

Install method: GitHub · runtime test inconclusive (L5 unknown)

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

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〕)

○ Ecosystem plugin

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
363b7d	○	○	○
2f1ac3	·	·	·

Install compatibility (by plugin version, dsh versions within)

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

363b7dgithub○ 3 ecosystem plugin2026-10-19

https://github.com/hy-sde/dsh-logseq

○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/hy-sde/dsh-logseq (version unstated)

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

L1 static

Not tested

L2 static

Not tested

L3 static

Unknown

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-logseq@363b7d@dsh0.2.1-rc.2 · profile: l4-sandbox

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

View checks & evidence

L1 · Found– Not tested

not in scope for web smoke; see prior standard-profile records

L2 · Structured– Not tested

not in scope for web smoke; see prior standard-profile records

L3 · Install spec? Unknown

↳ carried from earlier record dsh-logseq@2f1ac3@dsh0.2.1-alpha.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED? Unknown

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

no install command parsed

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-19

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 1.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 1.8s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:hy-sde/dsh-logseq · install mode reused L4 scratch

check took: 263ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 263ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

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

verdict not-found · entries 149

phases: active 121 · null 28

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-17Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: github · https://github.com/hy-sde/dsh-logseq (version unstated)

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

L1 static

Not tested

L2 static

Not tested

L3 static

Unknown

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-logseq@363b7d@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-17 · expires: 2026-10-24

View checks & evidence

L1 · Found– Not tested

not in scope for web smoke; see prior standard-profile records

L2 · Structured– Not tested

not in scope for web smoke; see prior standard-profile records

L3 · Install spec? Unknown

↳ carried from earlier record dsh-logseq@2f1ac3@dsh0.2.1-alpha.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED? Unknown

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

no install command parsed

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-17

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.6s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.6s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.6s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:hy-sde/dsh-logseq · install mode reused L4 scratch

check took: 2.6s

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 2.6s

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

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

verdict not-found · entries 149

phases: active 121 · null 28

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-14Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: github · https://github.com/hy-sde/dsh-logseq (version unstated)

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

L1 static

Not tested

L2 static

Not tested

L3 static

Unknown

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-logseq@363b7d@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence

L1 · Found– Not tested

not in scope for web smoke; see prior standard-profile records

L2 · Structured– Not tested

not in scope for web smoke; see prior standard-profile records

L3 · Install spec? Unknown

↳ carried from earlier record dsh-logseq@2f1ac3@dsh0.2.1-alpha.2 (l3-fullscan)

Install command parsedL3.1_INSTALL_COMMAND_PARSED? Unknown

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

no install command parsed

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-14

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.2s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.2s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:hy-sde/dsh-logseq · channel GitHub source · outcome ran · exit 0

check took: 2.2s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:hy-sde/dsh-logseq · install mode reused L4 scratch

check took: 148ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 148ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

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

verdict not-found · entries 149

phases: active 120 · null 28 · loading 1

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.

2f1ac3local2026-10-14

Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem 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-logseqAutomated review · daily

Static low, dynamic medium — stricter wins → overall medium.

static low→dynamic medium→overall medium

0 critical·0 high

mediumoverall · medium

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.1.7-rc.2

scanned version0.1.7-rc.2git2026-10-21

current version0.1.7-rc.2same version

vet verdictclean · git

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

show static findings (5)

criticalshellExec · shellpackages/logseq/tool-logseq/src/logseq.ts:334
const { env } = await exec(argv)
criticalshellExec · shellpackages/logseq/tool-logseq/src/logseq.ts:367
const { env } = await exec(argv)
warningshellExec · shellpackages/logseq/logseq-graph/src/cli.ts:67
execFile(cliPath, full, { timeout: timeoutMs, maxBuffer, windowsHide: true }, (error, stdout, stderr) => {
warningshellExec · shellpackages/logseq/tool-logseq/src/cli-check.ts:17
execFile(cliPath, ['--version'], { timeout: 8000, windowsHide: true }, (err, _stdout, stderr) => {
warningshellExec · shellpackages/logseq/tool-logseq/src/logseq.ts:76
execFile(cmd, args, {

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

highest grademedium

merged intooverall medium

audited at2026-10-19

findings0 critical·0 high1 medium / 1 low hidden

show 2 audit findings

mediumModel-controlled arbitrary file path passed to logseq_graph export/importpackages/logseq/tool-logseq/src/logseq.ts
The `logseq_graph` tool forwards the model-supplied `file` argument straight into the CLI's `graph export/import --file`. A prompt-injected model can export the entire graph (all notes) to any writable path, or import an attacker-crafted EDN/sqlite file to overwrite/clobber the graph, with no path confinement or allowlist. The underlying CLI performs the IO, but the plugin provides the unvalidated channel.
lowConfigurable cliPath rootDir are executed/used without validationpackages/logseq/logseq-graph/src/service.ts
The executable spawned by execFile is taken from deployment config. If any part of that config can be influenced by untrusted sources, an arbitrary binary could be executed. With trusted loader config this is only a hardening gap; no shell is involved, so normal tool arguments cannot inject commands.

Logseq CLI wrapper; execFile argv keeps shell injection out, but logseq_graph passes model-controlled file paths to export/import with no confinement.

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-09-06

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/hy-sde/dsh-logseq

Plugin notes

What is @hy-sde/dsh-logseq?

@hy-sde/dsh-logseq is an ecosystem plugin maintained by @hy-sde: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing it adds no plugin capability; use the source repository directly. It is cataloged on dsh.so as a Knowledge entry, with a public source repository and automated static security scan.

How do I install @hy-sde/dsh-logseq?

This is an ecosystem plugin: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing one adds no plugin capability; use the source repository directly. Its level reads L5 · Ecosystem plugin; 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

@hy-sde/dsh-logseq

What it doesAI

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README