Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Edge TTS voice plugin that reads assistant replies aloud with auto-read toggle and voice settings panel.
- Reads assistant replies aloud
- Auto-read toggle
- Voice settings panel, free no API key
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 @memef1f1y/dsh-plugin-ttsInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.1
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
current (registry 2026-11-15) · 9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-08 · 9 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-23 → 11-08 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-26 → 11-11 · 44 points
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
09-26 → 11-14 · 46 points
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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.0-rc.6 ×1
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.7.2 | ✓ | · | · | · | · |
| 0.6.7 | ✓ | ◐ | ✓ | ✓ | ✓ |
| 0.6.4 | · | · | · | · | · |
| 0.3.1 | · | · | · | · | · |
| v0.3.1 | · | · | · | · | · |
0.7.2npm✓ 1 runtime-verified2026-11-14
@memef1f1y/dsh-plugin-tts
✓dsh 0.2.2-rc.12026-11-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.7.2
ID: dsh-plugin-tts@0.7.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.6.7npm✓ 6 runtime-verified◐ 1 testing2026-11-10
@memef1f1y/dsh-plugin-tts
✓dsh 0.2.2-rc.12026-11-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-10 · expires: 2026-11-17
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◐dsh 0.2.2-alpha.22026-11-04L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
active in loader tree (150 entries)
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.32026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.3
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.7
ID: dsh-plugin-tts@0.6.7@dsh0.2.1-alpha.3 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.6.4npm✓ 4 runtime-verified2026-10-10
@memef1f1y/dsh-plugin-tts
✓dsh 0.2.1-alpha.22026-10-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.4
ID: dsh-plugin-tts@0.6.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.4
ID: dsh-plugin-tts@0.6.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.4
ID: dsh-plugin-tts@0.6.4@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @memef1f1y/dsh-plugin-tts@0.6.4
ID: dsh-plugin-tts@0.6.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.3.1npm2026-09-26
@memef1f1y/dsh-plugin-tts
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.3.1github✓ 3 runtime-verified2026-09-25
https://github.com/1624318455/dsh-plugin-tts
✓dsh 0.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/1624318455/dsh-plugin-tts#v0.3.1
ID: dsh-plugin-tts@v0.3.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/1624318455/dsh-plugin-tts#v0.3.1
ID: dsh-plugin-tts@v0.3.1@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/1624318455/dsh-plugin-tts#v0.3.1
ID: dsh-plugin-tts@v0.3.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge)``[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-tts/?ref=badge-install)`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.
Static low; dynamic high (authoritative when present) → overall high.
v0.7.2dsh manifest0.7.2npm2026-11-140.7.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
lib/index.mjs:230const child = spawn(process.execPath, argv, { - warningchildProcess · code-exec
lib/index.mjs:559const p = spawn(cfg.binary, ['--model', cfg.model, '--output_file', wavPath], { - warningnetIp · network
lib/index.mjs:367baseUrl: 'http://127.0.0.1:4892', - warningnetIp · network
lib/index.mjs:589baseUrl: 'http://127.0.0.1:7880', - warningnetIp · network
lib/index.mjs:715baseUrl: 'http://127.0.0.1:7890', - warningfsWrite · files
lib/index.mjs:115fs.writeFileSync(outPath, buf);
show 5 audit findings
- highProvider 'local-piper' spawns an arbitrary executable path taken from the /speak request body
lib/index.mjsPOST /dsh-tts-api/speak with {"provider":"local-piper","custom":{"piperBinary":"<any executable>","piperModel":"x"}} launches any program on the host as the dsh user, with two attacker-chosen arguments and attacker-chosen stdin content. No allowlist, no path check and no 'this must be configured by the user' gate exists; the binary path arrives per request. Binaries that read their script/commands from stdin (e.g. cmd.exe on Windows) escalate this to full command execution.
- mediumUnauthenticated SSRF: caller-supplied baseUrl is fetched and the response is reflected
lib/index.mjsGET /dsh-tts-api/rvc-files (and /index-voices, /cosy-voices, and the baseUrl in provider 'custom' used by /speak, /gsv-test, /diagnose, /rvc-compact-index) lets any caller make the dsh host issue HTTP requests to arbitrary host:port and read back the parsed JSON body or the error text. This turns the plugin into an internal-network probe / limited response-disclosure proxy for loopback and intranet addresses. Only the fixed path suffix ('/files?kind=', '/voices', '/convert', ...) is appended, which limits but does not remove the exposure.
- mediumVoice-pack install verifies sha256 against the same untrusted manifest and writes attacker-chosen .pth/.index files
lib/index.mjsThe integrity check is circular: model.url, model.sha256 and model.size all come from the manifest served by the caller-supplied registry URL, so an attacker who can reach POST /dsh-tts-api/rvc-pack-install (or who convinces the user to add their registry) can place an arbitrary .pth/.index payload into ~/.dsh/tts-rvc/packs/<id>/. The RVC backend loads .pth models via torch.load (pickle), so a malicious pack becomes code execution when the user selects that voice. installPack also records the path in installed.json, making the payload look like a legitimate installed voice.
- mediumpackId '..' escapes packsDir in rvc-pack-uninstall and recursively deletes ~/.dsh/tts-rvc
lib/index.mjsThe sanitiser keeps '.' and '-', so packId '..' yields stem '..' and path.join(packsDir(), '..') normalises to ~/.dsh/tts-rvc. POST /dsh-tts-api/rvc-pack-uninstall {"packId":".."} then rmSync -rf's the whole tts-rvc directory, destroying settings.json (which holds the Google Cloud API key), the calibration cache, the diagnostics log and every installed pack. Same pattern exists in installPack, where packId '..' writes '...pth' one level above the packs dir.
- lowGoogle Cloud API key stored in cleartext in a default-permission file under ~/.dsh/tts-rvc
lib/index.mjsThe API key is persisted unencrypted with the process umask (typically 0644), so any other local account or a backup/sync of the home directory exposes a billable Google Cloud credential. The GET route correctly returns only the last 4 characters, and the key is also placed in the request URL query string (?key=...), which can end up in proxy/HTTP logs.
Unauthenticated local TTS routes let a caller spawn an arbitrary executable (local-piper), proxy requests to arbitrary URLs, and install/delete files under ~/.dsh/tts-rvc.
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-11-10 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 58 · Forks: 6
• 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).
Frequently asked questions
What is dsh-plugin-tts?
dsh-plugin-tts 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-plugin-tts?
Run dsh plugin --profile web add @memef1f1y/dsh-plugin-tts in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-11-15 (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.