Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Flips the DeepSeek Harness web composer keymap so Enter inserts a newline and Cmd/Ctrl+Enter sends, leaving IME input untouched.
- Enter inserts a newline in the composer instead of sending
- Cmd+Enter (macOS) / Ctrl+Enter (Win/Linux) sends the message
- IME composition and slash/command menus keep their original Enter behavior
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:yonchicy/dsh-composer-modentersecurity scan passed · default branch source
Install method: GitHub · sandbox install ok, web smoke failed (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.
9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-28 → 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
10-03 → 11-08 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| b1161a | ✓ | ✓ | ✓ | ✓ | ✓ |
| 1b501d | ✗ | · | · | · | · |
b1161agithub✓ 9 runtime-verified2026-11-05
https://github.com/yonchicy/dsh-composer-modenter
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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.7-rc.22026-09-28L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-28 · expires: 2026-10-05
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
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-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter (version unstated)
ID: dsh-composer-modenter@b1161a@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1b501dgithub1 failed2026-11-12
https://github.com/yonchicy/dsh-composer-modenter
✗dsh 0.2.2-rc.12026-11-12L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/yonchicy/dsh-composer-modenter#1b501da55fae5b5c697c19a2a356e93b6ce49af4
ID: dsh-composer-modenter@1b501da55fae5b5c697c19a2a356e93b6ce49af4@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
↳ carried from earlier record dsh-composer-modenter@b1161a@dsh0.2.2-rc.1 (l4-sandbox)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-composer-modenter/?ref=badge)``[](https://www.dsh.so/artifact/dsh-composer-modenter/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-composer-modenter/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-composer-modenter/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-composer-modenter/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-composer-modenter/?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 no conclusion (static stands) → overall low.
v1.0.0dsh manifest1.0.0git2026-11-131.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
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-09-28 · activity: Stable
• Repo created: 2026-09-28
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 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 @yonchicy/dsh-composer-modenter?
@yonchicy/dsh-composer-modenter 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 @yonchicy/dsh-composer-modenter?
Run dsh plugin --profile web add github:yonchicy/dsh-composer-modenter 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-11-13 (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.