@Dingpenghui-good/dsh-obsidian-sync avatar

@Dingpenghui-good/dsh-obsidian-sync

PluginKnowledgeMemoryFileStorage
Verification
L4 · Install tested
Failed
Risk
Critical
Health
Active
Trust
Silver

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

What it doesAI

Searches an Obsidian vault by keyword (CJK-aware) and idempotently archives DSH sessions as Markdown notes with YAML frontmatter.

  • On-demand Obsidian keyword search with CJK bigram tokenization
  • Idempotent session archiving to vault/04 Archive/ as notes
  • Inverted index with 60s incremental rebuild, no prompt injection
knowledgeAImemoryAIfileAIstorageAI

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 @dingpenghui/dsh-obsidian-sync
verified 3.4.8

Install method: npm · sandbox install ok, web smoke failed (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
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 \ dshdsh 0.2.1-rc.2
current
dsh 0.2.1-alpha.2
3.4.8✗·
3.4.7·✗
v3.4.7··
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
3.4.8npm1 failed2026-10-21

@dingpenghui/dsh-obsidian-sync

✗dsh 0.2.1-rc.2current2026-10-21L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · @dingpenghui/dsh-obsidian-sync@3.4.8
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-obsidian-sync-2@3.4.8@dsh0.2.1-rc.2 · profile: l3-fullscan

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

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-21
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-21
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 2.8s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 2.8s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 2.8s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20
spec @dingpenghui/dsh-obsidian-sync · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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

3.4.7npm1 failed2026-10-18

@dingpenghui/dsh-obsidian-sync

✗dsh 0.2.1-alpha.22026-10-15L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · @dingpenghui/dsh-obsidian-sync@3.4.7
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-obsidian-sync-2@3.4.7@dsh0.2.1-alpha.2 · profile: l3-fullscan

Issued: 2026-10-15 · expires: 2026-10-22

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-21
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-21
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 4.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 4.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec @dingpenghui/dsh-obsidian-sync · channel npm package · outcome ran · exit 0
check took: 4.0s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec @dingpenghui/dsh-obsidian-sync · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

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

v3.4.7github2026-10-14

https://github.com/Dingpenghui-good/dsh-obsidian-sync

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

Author badges

Embed the official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/dsh-obsidian-sync-2.svg)](https://www.dsh.so/artifact/dsh-obsidian-sync-2/)`

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-obsidian-sync-2Automated review · daily

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

static low→dynamic high→overall high
0 critical·0 high
highoverall · high
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv3.4.8dsh manifest
scanned version3.4.8npm2026-10-21
current version3.4.8same version
vet verdictclean · npm

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

show static findings (6)
  • criticalshellExec · shelllib/index.js:332

    if (execSync("git add -A && git status --porcelain", {

  • criticalshellExec · shelllib/index.js:336

    }).trim().length > 0) execSync("git commit -m \"daily-review: " + dateStr + " 归档沉淀(" + todayFiles.length + " 篇)\" && git push", {

  • criticalshellExec · shelllib/index.js:401

    if (execSync("git add -A && git status --porcelain", {

  • criticalshellExec · shellsrc/index.ts:452

    const out = execSync('git add -A && git status --porcelain', {

  • criticalshellExec · shellsrc/index.ts:456

    execSync('git commit -m "daily-review: ' + dateStr + ' 归档沉淀(' + todayFiles.length + ' 篇)" && git push', {

  • criticalshellExec · shellsrc/index.ts:529

    const out = execSync('git add -A && git status --porcelain', { cwd: currentVaultPath(), timeout: 15000, encoding: 'utf-8' })

2model reads redacted source context · never executes plugin code
highest gradehigh
merged intooverall high
audited at2026-10-19
findings0 critical·1 high1 medium / 1 low hidden
show 3 audit findings
  • highSession title (and existing vault file names) reach execSync git command with only quote escaping — backtick command substitution executeslib/index.js

    sanitizeTitleForFilename strips slashes, quotes, pipe and parentheses but not backticks, '$', ';' or '&'. Inside double quotes those characters are still live to the shell, so a title such as fix `curl${IFS}x -o/tmp/y;sh${IFS}/tmp/y` bug yields a file name that the shell expands via command substitution before git runs, executing arbitrary commands as the DSH process user. The same sink is reachable without model cooperation when a file already matching the date-shortId prefix exists in 04-Archive with a crafted name. The execSync runs inside try/catch so the failure is silent and only surface

  • mediumobsidian_read_note resolves user path against vault root with no '../' check, allowing reads outside the vaultlib/index.js

    Only leading slashes and backslashes are normalized; '..' segments survive, so path '../../AppData/Roaming/...' or an absolute-style traversal resolves to files outside the vault. The full body (frontmatter plus entire file text, no size cap) is returned to the model, i.e. exfiltratable in the transcript. Reachability depends on the dsh-fs service accepting the resolved target, which is plausible because the same plugin already needs danger-full-access for vault writes.

  • lowUnattended 60s pollers run 'git add -A && git commit && git push' on the whole vaultlib/index.js

    At 22:00/local Sunday the plugin stages every change in the vault (including unrelated edits and untracked files) and pushes to the configured remote without confirmation; if that remote is public or shared, private notes leave the machine silently. The behaviour is disclosed in the locale hint text, so this is a consent/scope gap rather than a hidden channel.

Host plugin escapes sandbox for vault writes and feeds a title-derived path into execSync('git commit ...'), permitting shell command injection; obsidian_read_note also lacks a ../ traversal check.

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

• Repo created: 2026-09-03

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/Dingpenghui-good/dsh-obsidian-sync

Was this page helpful?