Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH 第三方 Tabbit 插件:内置网关接入 Tabbit 国内版/国际版账号池、周期额度、模型用量倍率、每日签到与工具调用
Installation
dsh plugin --profile web add github:xianshengl487-star/dsh-connect-tabbit#v0.4.0Install method: GitHub · 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.1-rc.2 current |
|---|---|
| v0.4.0 | ✓ |
v0.4.0github✓ 1 runtime-verified2026-10-21
https://github.com/xianshengl487-star/dsh-connect-tabbit
✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/xianshengl487-star/dsh-connect-tabbit#v0.4.0
ID: dsh-connect-tabbit@v0.4.0@dsh0.2.1-rc.2 · profile: l4-sandbox
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-connect-tabbit/)``[](https://www.dsh.so/artifact/dsh-connect-tabbit/)`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 no conclusion — stricter wins → overall low.
v0.4.0dsh manifestv0.4.0git2026-10-21v0.4.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
lib/gateway.js:37defaultGatewayUrl: 'http://127.0.0.1:8800', - warningnetIp · network
lib/gateway.js:44defaultGatewayUrl: 'http://127.0.0.1:8801', - warningnetIp · network
lib/gateway.js:95this.baseUrl = normalizeBaseUrl(options.baseUrl, options.region?.defaultGatewayUrl ?? 'http://127.0.0.1:8800') - warningchildProcess · code-exec
lib/local-accounts.js:12const child = spawn('powershell.exe', ['-NoProfile', '-NonInteractive', '-Command', script], { windowsHide: true, stdio: ['pipe', 'pipe', 'i - warningbase64Decode · obfuscation
lib/local-accounts.js:11const script = 'Add-Type -AssemblyName System.Security; try { $v=[Convert]::FromBase64String([Console]::In.ReadToEnd()); $r=[Security.Crypto - warningchildProcess · code-exec
lib/login.js:87const child = spawn(binary, [ - warningnetIp · network
lib/shim.js:145return `http://127.0.0.1:${address.port}`
not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.
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-21
• Stars: ★ 0 · 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).
