Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Connects China Telecom TeleAI's Xingchen super-agent as an LLM provider in DSH using a corrected v1 HMAC-SHA256 cloud gateway signature.
- Adds TeleAgent as a login-and-run model provider inside DSH
- Fixes the 40104 unsupported sign version error with v1 two-round HMAC-SHA256 signing
- Includes credit balance and daily check-in plus an in-composer account bar
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 dsh-connect-teleagentInstall 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| 1.2.6 | ✓ |
1.2.6npm✓ 1 runtime-verified2026-11-10
dsh-connect-teleagent
✓dsh 0.2.2-rc.1current2026-11-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-connect-teleagent@1.2.6
ID: dsh-connect-teleagent-2@1.2.6@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-10 · expires: 2026-11-17
View checks & evidence
↳ carried from earlier record dsh-connect-teleagent-2@847539@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-teleagent-2@847539@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-teleagent-2@847539@dsh0.2.2-rc.1 (l3-fullscan)
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-connect-teleagent-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-connect-teleagent-2/?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 high; dynamic low (authoritative when present) → overall low.
v1.2.6dsh manifest1.2.6git2026-11-111.2.6same versionsuspicious · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalsecretSk · secrets
lib/product.js:11export const CHANNEL_API_KEY = 'sk-qvp4m6h9g20uM6PgYP7E';
show 2 audit findings
- lowHardcoded channel API key constant shipped in the plugin (value redacted in audited copy)
lib/product.js:11Used as `Authorization: Bearer ${CHANNEL_API_KEY}` on every inference request. The comment says this is the key embedded in the official desktop client, i.e. a shared vendor credential, not a user secret. In the audited source the value is the placeholder '***REDACTED***', so no live secret can be confirmed; even a real value would grant no access to user data, only to the vendor's own channel.
- lowLocal RPC route /api/teleagent-connect has no caller authentication, only a JSON content-type gate
lib/rpc.js:38The handler accepts any POST with content-type application/json and exposes status, credits.claim, config.set (writes ~/.dsh/teleagent/config.json) and login.submit/credential repair (overwrites the stored TeleAgent credential). A caller able to reach the host HTTP server - another local process, or a web page via DNS rebinding - could replace the credential with one it controls, so subsequent user prompts are sent under that account. Reachability depends entirely on the DSH host's own origin/auth protection, which this plugin relies on and does not verify.
TeleAgent provider plugin: signing/credential code is confined to hardcoded teleai.com.cn hosts, no eval/exec/obfuscation; only low-risk items (embedded public client key, unauthenticated local RPC route).
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-07 · activity: Active
• Repo created: 2026-11-04
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/alvinhuang0509-design/dsh-connect-teleagent
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 @alvinhuang0509-design/dsh-connect-teleagent?
@alvinhuang0509-design/dsh-connect-teleagent 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 @alvinhuang0509-design/dsh-connect-teleagent?
Run dsh plugin --profile web add dsh-connect-teleagent 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-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.