This entry has been merged into: dsh-sound-lab — verification records were moved there; this page is kept as an archive.

dsh-event-sounds avatar

dsh-event-sounds

语音控制插件(安洁莉娜「hirari do~」)

PluginInterface & LayoutMediaNotificationsFile
Verification
L4 · Install tested
stale
Risk
Out of scope
Health
Stable
Trust
Silver

Install verification: sandbox install passed (L4) · runtime test (L5) pending · tested on dsh 0.1.1-rc.2 · last checked Install verification details →

Data as of (UTC)

What it doesAI

Customize DSH Web GUI sound events with AI voice lines and your own sound library via a sound lab.

  • Pick sounds for 4 trigger events: session end, popup, permission, stop
  • Generate AI character voice lines and upload custom sound library
  • Draggable floating ball with 3 appearances and dual persisted config
interfaceAInotificationAIfileAI

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:miiaowuwu/dsh-event-sounds

Install method: GitHub · sandbox install passed (L4) · runtime test (L5) pending · verified on dsh 0.1.1-rc.2

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.1.1-rc.2
v1.2.0·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
v1.2.0github2026-08-24

https://github.com/miiaowuwu/dsh-event-sounds

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

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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-event-sounds.svg)](https://www.dsh.so/artifact/dsh-event-sounds/?ref=badge)`

dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.

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-event-soundsAutomated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low
vet findings0 critical·0 high·2 medium
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv1.2.0dsh manifest
scanned version1.2.0git2026-08-26
current versionv1.2.0version moved on
vet verdictclean · git

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

show static findings (5)
  • criticalexfilEndpoint · networktools/api/tts_api.py:242

    ('0x0.st', 'https://0x0.st', 'file', None, 'text'),

  • warningfsWrite · fileslib/index.js:239

    await fs.writeFile(CONFIG_FILE, JSON.stringify(Object.assign({}, cfg, { [TTS_CONFIG_KEY]: next }), null, 2), "utf8");

  • warningfsWrite · fileslib/index.js:453

    await fs.writeFile(MANIFEST_FILE, JSON.stringify({ [MANIFEST_KEY]: sounds }, null, 2), "utf8");

  • warningfsWrite · fileslib/index.js:535

    await fs.writeFile(CONFIG_FILE, JSON.stringify(body, null, 2), "utf8");

  • warningchildProcess · code-exectools/install.mjs:21

    import { spawnSync, spawn } from "node:child_process";

2model reads redacted source context · never executes plugin code

no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.

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-08-22 · activity: Stable

• Repo created: 2026-08-17

• Stars: ★ 1 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/miiaowuwu/dsh-event-sounds

Frequently asked questions

What is dsh-event-sounds?

dsh-event-sounds is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.

Is dsh.so or this plugin page official?

dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.

How do I install dsh-event-sounds?

Run dsh plugin --profile web add github:miiaowuwu/dsh-event-sounds in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.

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, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.

How fresh is the data on this page?

The data on this page is as of 2026-10-22 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.

Was this page helpful?