Codex（ChatGPT Plus/Pro）订阅接入 DSH：展示 5 小时与一周额度、重置时间与重置券并支持一键重置；读取额度时自动把订阅模型接进模型选择器；access token 到期前自动续期。无需填写 API key。Codex (ChatGPT Plus/Pro) subscription for DSH: quota panel with one-click reset, subscription model routing, and token upkeep.
Install verification: runtime verified (L5) · 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
Adds a Codex (ChatGPT Plus/Pro) subscription panel to DSH with quota display, one-click reset and subscription model routing.
- Quota panel showing Codex subscription usage
- One-click quota reset from the panel
- Routes requests via subscription models with token upkeep
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.
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); the npm pair from every snapshot.
6 samples (roughly every 2 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 10-30 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-05 → 10-30 · 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
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:mia-wong1016/dsh-codex-plus#v0.1.7Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.5
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.5-rc.2 || ^0.2.0-rc.1 ×1
✓ Running dsh 0.2.2-rc.1 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.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v0.1.7 | ✓ | ✓ | ✓ | · | · |
| v0.1.4 | · | · | · | ✓ | ✓ |
| v0.1.1 | · | · | · | · | · |
v0.1.7github✓ 3 runtime-verified2026-11-04
https://github.com/mia-wong1016/dsh-codex-plus
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.7
ID: dsh-codex-plus@v0.1.7@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.7
ID: dsh-codex-plus@v0.1.7@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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/mia-wong1016/dsh-codex-plus#v0.1.7
ID: dsh-codex-plus@v0.1.7@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.4github✓ 5 runtime-verified2026-10-11
https://github.com/mia-wong1016/dsh-codex-plus
✓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/mia-wong1016/dsh-codex-plus#v0.1.4
ID: dsh-codex-plus@v0.1.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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/mia-wong1016/dsh-codex-plus#v0.1.4
ID: dsh-codex-plus@v0.1.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.4
ID: dsh-codex-plus@v0.1.4@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.4
ID: dsh-codex-plus@v0.1.4@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.4
ID: dsh-codex-plus@v0.1.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.1github✓ 1 runtime-verified2026-09-21
https://github.com/mia-wong1016/dsh-codex-plus
✓dsh 0.1.6-alpha.22026-09-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/mia-wong1016/dsh-codex-plus#v0.1.1
ID: dsh-codex-plus@v0.1.1@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
View checks & evidence
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-codex-plus@v0.1.7@dsh0.2.2-rc.1 (l3-fullscan)
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-codex-plus/?ref=badge)``[](https://www.dsh.so/artifact/dsh-codex-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-codex-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-codex-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-codex-plus/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-codex-plus/?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.7dsh manifestv0.1.7git2026-11-05v0.1.7same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalspawnShell · shell
lib/bridge.js:103return spawn(file, args, { ...options, shell: true }) - warningchildProcess · code-exec
lib/bridge.js:105return spawn(bin, args, options)
show 1 audit findings
- mediumWindows cmd.exe injection when spawning a .cmd codex shim with agent-controlled model/effort args
lib/bridge.js:103Node joins file + args into one command line for cmd.exe without escaping when shell:true. reachable on Windows whenever resolveCli()/resolveOnPath() resolves the npm shim (windowsCandidates pushes APPDATA\npm\codex.cmd, WIN_EXTS prefers .EXE but .CMD is probed). runTask() builds argv as [bin,'exec','--json','--skip-git-repo-check','-s',sandbox,'-m',String(model),'-c','model_reasoning_effort='+JSON.stringify(String(effort)),'-'] where model/effort come from the free-form parameters of the LLM-callable 'codex' tool (host.js). A value such as model='x & calc' therefore runs an arbitrary command
Windows-only command injection via shell:true when spawning a codex .cmd shim with agent-supplied model/effort; token handling and HTTP routes otherwise stay local and same-origin.
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-10-12 · activity: Active
• Repo created: 2026-09-21
• Stars: ★ 0 · Forks: 0
• 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 @mia-wong1016/dsh-codex-plus?
@mia-wong1016/dsh-codex-plus 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 @mia-wong1016/dsh-codex-plus?
Run dsh plugin --profile web add github:mia-wong1016/dsh-codex-plus#v0.1.7 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-05 (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.