Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · 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
Tiered model routing plugin for DeepSeek Harness with think/build tiers, vision delegation, and image generation.
- Think/build tiered routing
- Vision delegation to specialized models
- Image generation support
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:llmpolska/oh-my-dsh#v0.1.0Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
5 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-09 · 5 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-01 → 10-19 · 3 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
Based on 1 requirement(s) across 12 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×12
✗ Running dsh 0.2.2-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version oh-my-dsh-10@0.1.0 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)
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.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.0 | ✗ | ✗ | ✓ | ✓ | ✓ |
v0.1.0github✓ 13 runtime-verified2 failed2026-11-14
https://github.com/llmpolska/oh-my-dsh
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@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: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@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.
✓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/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
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.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/llmpolska/oh-my-dsh#v0.1.0
ID: oh-my-dsh-10@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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/oh-my-dsh-10/?ref=badge)``[](https://www.dsh.so/artifact/oh-my-dsh-10/?ref=badge-install)``[](https://www.dsh.so/artifact/oh-my-dsh-10/?ref=badge-install)``[](https://www.dsh.so/artifact/oh-my-dsh-10/?ref=badge-install)``[](https://www.dsh.so/artifact/oh-my-dsh-10/?ref=badge-install)``[](https://www.dsh.so/artifact/oh-my-dsh-10/?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 medium (authoritative when present) → overall medium.
v0.1.0dsh manifestv0.1.0git2026-11-17v0.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticaldestructiveRm · destructive
lib/client.js:334'High-impact guard — deny rm -rf / sudo / force push / secret edits on the build tier',
show 5 audit findings
- mediumReplays the ChatGPT OAuth token with a spoofed codex_cli_rs client to bypass Cloudflare
lib/codex-image.js:80readCodexOAuth() reads $DSH_HOME/.openai-codex-auth.json and the access token is sent to https://chatgpt.com/backend-api/codex/images/generations with headers forged to look like the official Codex CLI, explicitly to pass Cloudflare (comment: '/api/codex/... alias is bot-blocked for raw Node fetch'). The destination is the token's own issuer, so this is not exfiltration to an unrelated third party, but it uses credentials outside their intended client and violates the provider's client controls, risking account suspension/ban.
- mediumGET /omd/config returns the stored inline image API key in plaintext
lib/config.js:103viewFromState() copies the inline image API key into the flat view, and the /omd GET handler answers with 'config: viewFromState(cfg.state)'. The page fetches /omd/config without any credential, and loadConfig()/readFresh() and adoptRuntimeDefaults() call settings.describe({ redactSecrets: false }), so the unredacted secret is re-emitted over an endpoint with no auth/origin check. Any local client (or a page able to read same-origin/local responses) gets the key.
- mediumUnauthenticated POST /omd/config accepts cross-site writes that redirect image credentials
lib/index.jsThe mutation handler checks no Origin/Referer, no auth token and ignores Content-Type, while readBody+JSON.parse accept any simple (preflight-free) request a web page can send to the local server. validatePatch only length-checks strings, so an attacker page can set imageProvider:'' + imageBaseUrl:'https://evil' (and imageApiKeyEnv/imageOutDir). On the next omd_image/`/omd image` the plugin resolves the stored key (inline or via credentials/env) and sends it as 'Authorization: Bearer <key>' to the attacker's host, and writes the returned bytes to an attacker-chosen directory.
- lowimageOutDir is only length-checked and is resolved into an arbitrary filesystem path
lib/agent.jsoutDir comes from the config (validated only as 'string with length <= 512'), may be absolute or contain '..', and resolve(process.cwd(), outDir) then mkdirSync/writeFileSync there. An absolute outDir such as /home/user/.config/... makes the plugin create directories and write files outside the workspace; with the unauthenticated config write above, the bytes are attacker-influenced and the filename/extension are predictable (omd-<timestamp>-<seq>.<png|jpg|webp|gif>).
- lowSilently adopts itself as the global default agent preset on first boot
lib/index.jsensurePresetInstalled() writes the preset into $DSH_HOME/.agent-presets and adoptPresetAsDefault() then rewrites the user's global agent-presets default without any prompt or confirmation. Every new session therefore runs under this plugin's routing/interception (including monkey-patched llm streaming and prompt admission), which is a global behavior change the user did not explicitly approve.
Refuted the static critical (the Codex token only goes to its issuer), but the unauthenticated /omd endpoint leaks the stored image API key and accepts unauthenticated config writes.
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-16 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 1 · Forks: 1
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/llmpolska/oh-my-dsh
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 oh-my-dsh?
oh-my-dsh 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 oh-my-dsh?
Run dsh plugin --profile web add github:llmpolska/oh-my-dsh#v0.1.0 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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-17 (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.
