Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Bridges business projects to DSH by creating or resuming native sessions to run prompts and files, then returning AI replies and result files.
- Installs from npm into a DSH profile and loads after restart
- Settings → Project Integration page configures business projects
- Sessions run prompts and files inside the target workspace
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 @fevolq/terms-bridgeInstall method: npm · sandbox install ok, web smoke failed (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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| 0.3.0 | ✗ |
0.3.0npm1 failed2026-11-11
@fevolq/terms-bridge
✗dsh 0.2.2-rc.1current2026-11-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @fevolq/terms-bridge@0.3.0
ID: terms-bridge@0.3.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-11 · expires: 2026-11-18
View checks & evidence
↳ carried from earlier record terms-bridge@487307@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record terms-bridge@487307@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record terms-bridge@487307@dsh0.2.2-rc.1 (l3-fullscan)
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/terms-bridge/?ref=badge)`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 low (authoritative when present) → overall low.
v0.3.0dsh manifest0.3.0npm2026-11-110.3.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- warningnetIp · network
examples/download_result.py:20base = os.environ.get("DSH_API_BASE", "http://127.0.0.1:3080/api/terms-bridge").rstrip("/") - warningnetIp · network
examples/project_client.py:55base = os.environ.get("DSH_API_BASE", "http://127.0.0.1:3080/api/terms-bridge").rstrip("/") - warningnetIp · network
examples/upload_and_submit.py:28base = urlsplit(os.environ.get("DSH_API_BASE", "http://127.0.0.1:3080/api/terms-bridge").rstrip("/"))
show 2 audit findings
- lowRuntime artifacts dist/index.js and dist/client.js are not part of the audited source
package.jsonThe code that actually executes inside the DSH host and the web client is compiled output that was not harvested, so its network, filesystem and upload-handling behaviour cannot be verified; the hardened examples do not necessarily reflect it.
- lowExample clients send the bearer token over whatever scheme DSH_API_BASE specifies, including plaintext http
examples/project_client.pyThe validation accepts any http(s) origin; if a user points DSH_API_BASE at a non-loopback host over http, the request token and task payloads travel in cleartext. Defaults are loopback-only, so this requires operator misconfiguration.
Audited plugin exposes only metadata plus hardened stdlib Python examples; the shipped dist/ runtime is not in the harvest, so no concrete exploitable issue was found.
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-11-09 · activity: Active
• Repo created: 2026-11-03
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/fevolq/terms-bridge
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 @fevolq/terms-bridge?
@fevolq/terms-bridge 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 @fevolq/terms-bridge?
Run dsh plugin --profile web add @fevolq/terms-bridge in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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-11 (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.