Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
A SillyTavern-like text game agent that imports or creates character cards, generates story and candidate options, and plays scripted campaigns.
- Generates candidate options in separate rounds to avoid format drift
- Imports tavern cards or creates new cards from novels/scripts
- Uses retrieval and context compression to handle long conversations
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:flizzywine/dsh-tavern#v3.3security scan passed · source release v3.3
Install method: GitHub · runtime test inconclusive (L5 unknown) · 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-16) · 9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-11 · 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
10-02 → 11-11 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-28 → 11-14 · 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-28 → 11-14 · 44 points
Verification & Compatibility○ Ecosystem plugin
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
○ The author declares no dsh version requirement — install is not blocked by version.
| 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 |
|---|---|---|---|---|---|
| 3.2.0 | ○ | ○ | · | · | · |
| 3.1.3 | · | · | ✗ | ✗ | · |
| 2.7.0 | · | · | · | · | ✗ |
| 2.6.0 | · | · | · | · | · |
| 2.5.0 | · | · | · | · | · |
3.2.0npm○ 2 ecosystem plugin2026-11-04
dsh-profile-tavern
○dsh 0.2.2-rc.12026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-profile-tavern@3.2.0
ID: dsh-tavern-2@3.2.0@dsh0.2.2-rc.1 · profile: l5-web-smoke
Issued: 2026-11-04 · expires: 2027-02-02
View checks & evidence
not present in web-profile loader inventory
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-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: npm · dsh-profile-tavern@3.2.0
ID: dsh-tavern-2@3.2.0@dsh0.2.2-alpha.2 · profile: l5-web-smoke
Issued: 2026-11-04 · expires: 2027-02-02
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
3.1.3npm2 failed2026-10-30
dsh-profile-tavern
✗dsh 0.2.1-rc.52026-10-30Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-profile-tavern@3.1.3
ID: dsh-tavern-2@3.1.3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
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-26Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-profile-tavern@3.1.3
ID: dsh-tavern-2@3.1.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.7.0npm2 failed2026-10-18
dsh-profile-tavern
✗dsh 0.2.1-rc.22026-10-18Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-profile-tavern@2.7.0
ID: dsh-tavern-2@2.7.0@dsh0.2.1-rc.2 · profile: l5-web-smoke
Issued: 2026-10-18 · expires: 2027-01-16
View checks & evidence
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-15Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-profile-tavern@2.7.0
ID: dsh-tavern-2@2.7.0@dsh0.2.1-alpha.4 · profile: l5-web-smoke
Issued: 2026-10-15 · expires: 2027-01-13
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.6.0npm2026-10-13
dsh-profile-tavern
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
2.5.0npm2 failed2026-10-10
dsh-profile-tavern
✗dsh 0.2.1-alpha.22026-10-10Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-profile-tavern@2.5.0
ID: dsh-tavern-2@2.5.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
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-08Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-profile-tavern@2.5.0
ID: dsh-tavern-2@2.5.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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-tavern-2/?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.
Static low; dynamic medium (authoritative when present) → overall medium.
v3.3.0dsh manifestv3.3git2026-11-16v3.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show 2 audit findings
- mediumProfile bundle defaults the agent to danger-full-access sandbox with approval policy 'never'
tavern-plugin/cordis.patch.yml:5The bundle actively reconfigures the host harness so that every tool call runs with full filesystem/network reach and is never surfaced for user approval; combined with the tavern preset mounting tool-bash/tool-pwsh and tool-fs (write enabled), text that reaches the model — e.g. an imported community character card or fetched asset — can steer the model into shell/file operations that execute on the user's machine with no confirmation step. The bundle's own comment ('Tavern 默认完全权限') confirms this is the shipped default, not an opt-in.
- mediumTavern preset auto-loads user-supplied JavaScript from a persistent, agent-writable data directory
tavern-plugin/cordis.patch.yml:127A loader explicitly described as the single entry point for user code in a persistent data directory sits in the same preset as a write-enabled tool-fs and an approval-free shell. Anything able to influence agent behaviour (prompt injection from card/world-book text, or a downloaded asset pack) can drive a file write into that directory and obtain code execution on the next load, with no approval gate.
Mostly inert config/stub files, but the shipped cordis profile disables the sandbox and approvals and auto-loads user JS, so prompt-driven tool calls get unrestricted host execution.
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-16 · activity: Active
• Repo created: 2026-08-16
• Stars: ★ 1,626 · Forks: 109
• Health: Active — committed within last 30 days
Source
GitHub: github.com/flizzywine/dsh-tavern
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-tavern?
dsh-tavern is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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-tavern?
Run dsh plugin --profile web add github:flizzywine/dsh-tavern#v3.3 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-16 (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.
