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
Adds a password-protected login wall and reverse proxy for secure public access to a local DeepSeek Harness instance.
- Listens on port 8080, path /dsh, avoiding conflict with official web
- Requires login before reverse proxying to local 127.0.0.1 Harness
- Credentials remain local; package contains no real secrets
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:MrLukezy/dsh-cloud-gateway#v1.2.1Install method: GitHub · 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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-16 · 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
09-25 → 11-16 · 8 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.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 |
|---|---|---|---|---|---|
| v1.2.1 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.2.1github✓ 15 runtime-verified2026-11-16
https://github.com/MrLukezy/dsh-cloud-gateway
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-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.
✓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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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.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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dsh0.1.6-alpha.2 · profile: l4-sandbox
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/MrLukezy/dsh-cloud-gateway#v1.2.1
ID: dsh-cloud-gateway@v1.2.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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-cloud-gateway/?ref=badge)``[](https://www.dsh.so/artifact/dsh-cloud-gateway/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-gateway/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-gateway/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-gateway/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-cloud-gateway/?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.3.7dsh manifestv1.2.1git2026-11-17v1.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
index.js:122return new URL(req.url || "/", "http://127.0.0.1"); - warningnetIp · network
index.js:124return new URL("/", "http://127.0.0.1"); - warningfsWrite · files
index.js:63fs.writeFileSync(file, `${JSON.stringify(state, null, 2)}\n`, { mode: 0o600 }); - warningfsWrite · files
index.js:65fs.chmodSync(file, 0o600); - warningfsWrite · files
index.js:154fs.writeFileSync(manifestPath(dir), JSON.stringify(data, null, 2));
show 6 audit findings
- mediumAdmin login and session cookie travel over plain HTTP on 0.0.0.0 by default
index.js:21The listener speaks cleartext HTTP; the password posted to <basePath>/login and the dsh_gw session cookie cross the network unencrypted unless an external TLS terminator is used. Because cookieHeader only adds Secure when isHttps() is true (req.socket.encrypted, or trustProxy plus X-Forwarded-Proto), the default deployment sets a non-Secure 7-day cookie that a passive sniffer can replay for full Harness control.
- mediumProxy spoofs loopback Host and strips Sec-Fetch headers, defeating upstream loopback pinning
index.js:287The comment admits Harness pins settings.describe and other privileged RPCs to loopback even with --trusted-host. The proxy rewrites Host/Origin/Referer and removes the cross-site fence markers, so any authenticated session (including one obtained via finding 1) reaches the full privileged configuration plane and every route registered on the Harness webServer as trusted local traffic. The gateway login becomes the single, non-redundant security boundary.
- mediumUpload endpoint registered on the Harness web server performs no authentication of its own
index.js:191The handler never checks the session; it relies entirely on the gateway login wall and on the Harness port being loopback-only. Any client that can reach that port (misconfigured bind, another local process, or a browser request treated as same-origin) can POST JSON and write up to 20 MB of attacker-controlled bytes into $DSH_HOME/uploads, update manifest.json, and receive the absolute filesystem path in the response. Files planted this way can later be pulled into a conversation via the @token mention.
- lowPassword stored in plaintext in the state file and printed to the console
index.js:711The generated password is written verbatim to cloud-gateway-state.json (nextState.generatedPassword at line 707) and a user-chosen password is persisted the same way (userSettings.password at line 780), plus the credential is echoed into logs that may be captured by journald/container logging or terminal scrollback. Anyone with read access to those sinks obtains full admin access.
- lowLogin rate limit keys on spoofable X-Forwarded-For when trustProxy is enabled
index.js:109With trustProxy on and the listener directly reachable, an attacker sends a different X-Forwarded-For value per request and never hits the 10-attempts/10-minutes lockout, enabling offline-bounded but unlimited online password guessing against the single admin account.
- lowLogout only clears the cookie; stateless HMAC tokens stay valid for 7 days
index.js:534Tokens are pure HMAC payloads with no server-side revocation, so a token observed earlier (see the cleartext-transport finding) remains usable after logout or after the password is changed, for the full MAX_AGE window.
Login wall is sound, but default plain-HTTP on 0.0.0.0, a proxy that impersonates loopback to bypass upstream pinning, and an unauthenticated upload route leave concrete medium risk.
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-21 · activity: Active
• Repo created: 2026-08-17
• Stars: ★ 1 · 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 dsh-cloud-gateway?
dsh-cloud-gateway 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-cloud-gateway?
Run dsh plugin --profile web add github:MrLukezy/dsh-cloud-gateway#v1.2.1 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.
