Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Expose any local service on a random cloudflared domain with one password — QR code for LAN, QR + password for public, per-node routing managed in the DSH settings panel.
Installation
dsh plugin --profile web add dsh-service-portalInstall method: npm · runtime verified (L5)
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.1-rc.2 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| 1.0.3 | ✓ | · |
| 1.0.1 | · | ✓ |
| v0.8.8 | · | · |
1.0.3npm✓ 1 runtime-verified2026-10-21
dsh-service-portal
✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-service-portal@1.0.3
ID: dsh-service-portal@1.0.3@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
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.
1.0.1npm✓ 1 runtime-verified2026-10-18
dsh-service-portal
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-service-portal@1.0.1
ID: dsh-service-portal@1.0.1@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.
v0.8.8github2026-10-18
https://github.com/dingminhua/dsh-service-portal
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-service-portal/)``[](https://www.dsh.so/artifact/dsh-service-portal/)`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 — stricter wins → overall medium.
v1.0.4dsh manifest1.0.4npm2026-10-211.0.4same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
tools/check_plugin_stop.py:53"http://127.0.0.1:%d/_auth/health" % port, timeout=3) as res: - warningnetIp · network
tools/check_portal_form.py:37req = urllib.request.Request("http://127.0.0.1:%d%s" % (PORT, path), - warningnetIp · network
tools/check_portal_integration.py:83"lan_urls": ["http://192.168.1.5:8899"], "public_url": None, - warningnetIp · network
tools/check_portal_service_api.py:89code, _ = http("GET", "http://127.0.0.1:%d/_auth/health" % portal_port, - warningnetIp · network
tools/check_portal_service_api.py:100code, out = http("POST", "http://127.0.0.1:%d/_api/services" % portal_port, - warningnetIp · network
tools/check_portal_service_api.py:105code, out = http("GET", "http://127.0.0.1:%d/_api/services" % portal_port) - warningnetIp · network
tools/check_portal_settings_forward.py:55"http://127.0.0.1:%d/_api/state" % port, timeout=6) as res: - warningnetIp · network
tools/check_portal_status_running_services.py:100"http://127.0.0.1:%d/_auth/health" % port, timeout=3) as res: - warningnetIp · network
tools/check_portal_status_running_services.py:114"http://127.0.0.1:%d/_api/services" % port, data=body, - warningnetIp · network
tools/check_probe_button_browser.py:136url = "http://127.0.0.1:%d/" % port - warningnetIp · network
tools/check_probe_button_browser.py:167"http://127.0.0.1:%d/_api/shutdown" % port, data=b"", - warningnetIp · network
tools/check_shutdown_self_exit.py:66"http://127.0.0.1:%d/_api/shutdown" % port, data=b"", method="POST",
show 2 audit findings
- mediumPortal console is reachable from the LAN without a password by default
tools/check_portal_integration.py:120The auth gate treats every single-label/LAN host as an open class whenever the LAN password switch is off, and a freshly started portal reports lan_auth_enabled=False (tools/check_portal_settings_forward.py asserts 'before is False'). Anyone on the same network segment can therefore open the console without credentials and see the service list and internal upstream targets; the add-service path takes an arbitrary host:port (e.g. "target": "127.0.0.1:8810" in tools/check_portal_form.py:82), so if the management API sits behind the same host-based gate, a LAN peer gains a route to loopback-only
- lowRuntime entry point and portal implementation are missing from the audited source
package.json:23The code that actually runs — host route handlers, the auth gate, the reverse proxy and the cloudflared/Basic-Auth tunnel — is not present (lib/index.js, tools/portal_run.py, tools/portal_proxy.py, tools/tunnel_auth.py, tools/start_public_gui.py), although cordis.patch.yml names those scripts as the implementation. Their behaviour, target validation, credential generation and tunnel exposure could not be reviewed, and the static scan's warnings cannot be attributed to runtime code.
Only test tooling and manifests were supplied; the real entry point (lib/index.js) and portal implementation are absent. Concrete design risk: the portal console is passwordless for LAN clients by default.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-15
• Stars: ★ 1 · Forks: 1
• 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).