Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Provides a native DSH provider hub with OAuth, API channels, model discovery, failover, and logging.
- Official account OAuth support
- Model discovery and routing
- Failover and logging capabilities
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:HeWhenJay/dsh-provider-hub#v0.6.16Install 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.
11 samples (roughly every 7 days), 6 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-13 · 11 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
09-24 → 11-13 · 10 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 4 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×4
✗ 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 dsh-provider-hub@0.6.16 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.6.16 | ✗ | ✗ | ✓ | ✓ | ✓ |
v0.6.16github✓ 13 runtime-verified2 failed2026-11-14
https://github.com/HeWhenJay/dsh-provider-hub
✗dsh 0.2.1-rc.52026-10-30L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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-28L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-04
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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: github · https://github.com/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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.
✓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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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/HeWhenJay/dsh-provider-hub#v0.6.16
ID: dsh-provider-hub@v0.6.16@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-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · github:HeWhenJay/dsh-provider-hub#v0.6.16#v0.6.16
ID: dsh-provider-hub@v0.6.16@dshunknown · profile: l5-web-smoke
Issued: 2026-09-30 · expires: 2026-12-29
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/dsh-provider-hub/?ref=badge)``[](https://www.dsh.so/artifact/dsh-provider-hub/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-provider-hub/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-provider-hub/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-provider-hub/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-provider-hub/?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.6.16dsh manifestv0.6.16git2026-11-17v0.6.16same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
sidecar.js:63const child = spawn(command, args, { cwd, windowsHide: true, stdio: 'ignore' }); - warningchildProcess · code-exec
sidecar.js:237const child = spawn(this.executable, ['-config', this.configFile], { cwd: this.root, windowsHide: true, stdio: 'ignore' }); - warningnetIp · network
sidecar.js:131get baseURL() { return this.port ? `http://127.0.0.1:${this.port}` : ''; } - warningnetIp · network
sidecar.js:193const response = await fetch(`http://127.0.0.1:${port}/v1/models`, { headers: { authorization: `Bearer ${key}` }, signal: AbortSignal.timeou - warningnetIp · network
sidecar.js:302const targetBase = `http://127.0.0.1:${this.port}${paths[provider]}`;
show 4 audit findings
- mediumAuto-downloads and executes a third-party native binary whose integrity is anchored to a checksum fetched from the same GitHub release
sidecar.js:15apply() calls startAccountServiceInBackground(), and start()/performInstall() (also force-reachable via installAccountService and startAccountOAuth with install:true) fetch checksums.txt and the archive from the same release, extract it with `tar -xzf` (or PowerShell Expand-Archive) without validating entry paths, chmod 0700 and spawn the binary with the user's privileges for the whole session. If the upstream repository account or release assets are compromised, arbitrary native code runs on the host; the same-origin checksum does not defend against upstream compromise, and an already-present
- lowModel discovery fetches any caller-supplied http(s) URL with the stored provider key and without the private-address guard used elsewhere
index.jsPOST /api/provider-hub/models/discover takes a fully caller-controlled baseURL and issues a server-side GET with a Bearer key attached, with no host allowlist and no public-address/DNS pinning, in contrast to safeResearchURL/fetchPinnedResearchSource which deliberately block private ranges, rebinding and redirects. If the DSH management API is reachable by anyone other than the trusted UI user, this becomes an SSRF/probe primitive into localhost, LAN hosts and cloud metadata, optionally leaking a provider key to an attacker-chosen host.
- lowRelay allows unauthenticated requests from any local process when bound to 127.0.0.1 and no Origin/Forwarded/Authorization headers are present
index.jsAny process running on the same machine can call /v1/chat/completions and /v1/models without the relay key and spend the user's upstream provider credentials; the Origin/Forwarded checks do exclude browser-initiated and proxied traffic, so this is a deliberate local-trust choice rather than a CSRF bypass, and the same process could read the credentials store directly anyway.
- lowLLM-derived model metadata from untrusted web pages is persisted without evidence verification, affecting limits and cost estimates
index.jsDuring 'model specification research' the plugin fetches third-party pages, feeds their text into a research LLM prompt and accepts the returned maximumContextWindow/maxTokens/modelPricing/reasoningEfforts as long as they are well-formed (validatePracticalSpecification marks them llm-researched, in contrast to validateSpecification which requires the value to appear in official evidence). Attacker-authored content surfaced by web search can steer persisted context windows, pricing and thinking wire strings; impact is limited to wrong limits/cost accounting in DSH, not code execution.
Local LLM relay plugin that is mostly hardened, but auto-downloads and runs a third-party native sidecar binary, and its management-triggered outbound fetches lack the SSRF guards used elsewhere.
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-17 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 2 · 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 dsh-provider-hub?
dsh-provider-hub 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 dsh-provider-hub?
Run dsh plugin --profile web add github:HeWhenJay/dsh-provider-hub#v0.6.16 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.
