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 插件):按作息自己醒、刷抖音热榜/视频/评论、写两本日记。数据能力来自 dsh-douyin。
Installation
dsh plugin --profile web add github:sharkisyou/dsh-dy-whale#v0.2.1Install method: GitHub · 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 |
|---|---|
| v0.2.1 | ✗ |
v0.2.1github1 failed2026-10-28
https://github.com/sharkisyou/dsh-dy-whale
✗dsh 0.2.1-rc.3current2026-10-28L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/sharkisyou/dsh-dy-whale#v0.2.1
ID: dsh-dy-whale@v0.2.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
View checks & evidence
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:
`[](https://www.dsh.so/artifact/dsh-dy-whale/)`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.1dsh manifestv0.2.1git2026-10-28v0.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
lib/douyin-login.js:162const child = spawn(pythonOf(cfg), [bridgeOf(cfg), 'login-daemon'], { - warningshellExec · shell
lib/douyin-login.js:50execFileSync(c, ['-version'], { stdio: 'ignore' }) - warningshellExec · shell
lib/douyin-login.js:118execFileSync(ff, ['-hide_banner', '-loglevel', 'error', '-i', shot, '-vf', `crop=${QR_CROP}`, '-y', crop], { stdio: 'ignore' }) - warningshellExec · shell
lib/douyin-login.js:180execFileSync('pkill', ['-f', path.join(String(cfg.douyinRepo).trim(), 'data', 'browser-profile')], { stdio: 'ignore' }) - warningfsWrite · files
lib/douyin-login.js:119fs.writeFileSync(crop + '.json', JSON.stringify({ src: mtime })) - warningfsWrite · files
lib/douyin-login.js:218fs.writeFileSync(file, JSON.stringify({ action: 'submit_code', codes, at: new Date().toISOString() })) - warningfsWrite · files
lib/index.js:62fs.writeFileSync(CONFIG_FILE, JSON.stringify(DEFAULTS, null, 2) + '\n') - warningfsWrite · files
lib/index.js:73fs.writeFileSync(tmp, JSON.stringify(value, null, 2) + '\n') - warningfsWrite · files
lib/index.js:80try { fs.mkdirSync(DATA_DIR, { recursive: true }); fs.appendFileSync(LOG_FILE, line + '\n') } catch {}
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-26 · activity: Active
• Repo created: 2026-10-26
• 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).
