Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
What it does
飞书公告板:DSH 会话提问推到飞书私聊,回复原文回填原会话(宿主插件,含重复发送抑制)
Installation
dsh plugin --profile web add dsh-feishu-boardInstall 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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.3 current |
|---|---|
| 0.2.3 | ✗ |
0.2.3npm1 failed2026-10-28
dsh-feishu-board
✗dsh 0.2.1-rc.3current2026-10-28L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-feishu-board@0.2.3
ID: dsh-feishu-board@0.2.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
View checks & evidence
↳ carried from earlier record dsh-feishu-board@54a334@dsh0.2.1-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-feishu-board@54a334@dsh0.2.1-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-feishu-board@54a334@dsh0.2.1-rc.3 (l3-fullscan)
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:
`[](https://www.dsh.so/artifact/dsh-feishu-board/)`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.
Static low; dynamic no conclusion (static stands) → overall low.
v0.2.3dsh manifest0.2.3npm2026-10-280.2.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcess · code-exec
lark-cli-shim.js:104const p = spawn(process.execPath, [REAL, ...argv], { stdio: 'inherit', env: process.env }); - warningchildProcess · code-exec
lark-cli-shim.js:119const p = spawn(process.execPath, [REAL, ...argv], { stdio: ['inherit', 'pipe', 'inherit'], env: process.env }); - warningfsWrite · files
lark-cli-shim.js:89fs.writeFileSync(STATE, JSON.stringify(state)); - warningfsWrite · files
lark-cli-shim.js:97fs.appendFileSync(EVENTS, `${JSON.stringify({ - warningchildProcessImport · code-exec
lib/index.js:21import { execFile } from 'node:child_process'; - warningfsWrite · files
lib/index.js:85const status = (patch) => fs.writeFileSync(PF, JSON.stringify({ - warningfsWrite · files
lib/index.js:104const writeJsonl = (p, rows) => fs.writeFileSync(p, rows.map((r) => JSON.stringify(r)).join('\n') + '\n'); - warningfsWrite · files
lib/index.js:105const appendJsonl = (p, row) => fs.appendFileSync(p, JSON.stringify(row) + '\n');
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-27
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
