Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · 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
DSH sidebar panel that tracks each teammate's token usage for a chosen project and aggregates team totals on a self-hosted server.
- Each member picks one project to monitor; only its real usage is counted
- Collapsed view shows team projects and total tokens; expanded shows per-person usage
- Bottom-left peak/off-peak badge marks DeepSeek's current billing window
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.
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); the npm pair from every snapshot.
7 samples (roughly every 1 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
10-02 → 11-06 · 7 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-07 → 11-06 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:guooo1380/dsh-team-panelInstall 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 6bf1c5 | ✓ | ✓ | ✓ | ✓ | ✓ |
6bf1c5github✓ 10 runtime-verified2026-11-05
https://github.com/guooo1380/dsh-team-panel
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@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-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-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.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@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.42026-10-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-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.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/guooo1380/dsh-team-panel (version unstated)
ID: dsh-team-panel@6bf1c5@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-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.
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-team-panel/?ref=badge)``[](https://www.dsh.so/artifact/dsh-team-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-team-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-team-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-team-panel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-team-panel/?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 low (authoritative when present) → overall low.
v0.2.1dsh manifest0.2.1git2026-11-110.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningfsWrite · files
lib/index.js:177fs.writeFileSync(tmp, JSON.stringify(STATE, null, 2), 'utf8') - warningnetIp · network
lib/panel.js:339' <input data-el="inHub" maxlength="300" placeholder="http://192.168.1.10:7801"></div>', - warningnetIp · network
lib/team-hub.mjs:581` 管理页面 http://127.0.0.1:${ARGS.port}/admin?key=${team.adminKey}`, - warningnetIp · network
lib/team-hub.mjs:614' · 临时外网：另开一个窗口跑 cloudflared tunnel --url http://127.0.0.1:' + ARGS.port, - warningfsWrite · files
lib/team-hub.mjs:102fs.writeFileSync(tmp, JSON.stringify(DATA, null, 2), 'utf8') - warningfsWrite · files
lib/team-hub.mjs:628fs.writeFileSync(ARGS.data, JSON.stringify(DATA, null, 2), 'utf8') - warningnetIp · network
scripts/ci.mjs:79const res = await fetch(`http://127.0.0.1:${port}/api/health`, { signal: ctrl.signal }) - warningnetIp · network
scripts/ci.mjs:145const url = `http://127.0.0.1:${port}` - warningnetIp · network
scripts/fake-device.mjs:47hub地址 团队服务器地址，例如 http://127.0.0.1:7801 - warningnetIp · network
scripts/fake-device.mjs:126console.log(' 4) 地址和端口对吗？默认 http://127.0.0.1:7801\n') - warningnetIp · network
scripts/hub-info.mjs:59const res = await fetch(`http://127.0.0.1:${PORT}/api/health`, { signal: ctrl.signal }) - warningnetIp · network
scripts/hub-info.mjs:76console.log(` 管理页面 http://127.0.0.1:${PORT}/admin?key=${team.adminKey}`)
show 4 audit findings
- lowMember token and invite code are persisted in state.json with default (world-readable) file permissions
lib/index.js:177STATE contains memberToken, inviteCode and teamId (emptyState, lib/index.js:118-136). No mode option is passed, so with a typical umask the directory is 0755 and the file 0644 — any other local account on a shared machine can read the member token, then impersonate this member against the team hub (report forged usage, rename the member) and pull the full team snapshot. Impact is limited to multi-user local access.
- lowMember token is sent as a URL query parameter and the hub URL may default to plain HTTP
lib/index.js:419normalizeHubUrl (lib/index.js:305-310) prepends http:// when no scheme is given and does not require TLS. The member token then travels in the request line of GET /api/snapshot, so it can be captured by a network observer and is routinely written to reverse-proxy/server access logs, even when the body-based report path would be less exposed.
- lowBrowser trust fence fails open when the connection service is missing or throws
lib/index.js:547rejected() returns false (= not rejected) whenever ctx.get('connection') is unavailable, the method is absent, or the call throws (lib/index.js:553-555). In that state all nine /dsh-team/* routes become unauthenticated: /state discloses hubUrl/teamId/inviteCode, /config and /join let a caller repoint hubUrl at an arbitrary server so subsequent usage, hostname and local project paths are pushed there, and /project probes arbitrary directory existence. The plugin does declare inject: ['webServer','connection'], so this path should normally be unreachable.
- lowFull local project path and machine hostname are reported to the team hub and shown to all teammates
lib/index.js:362reportPayload (lib/index.js:350-375) also carries machine: os.hostname(), and every subsequent pushUsage/heartbeat re-sends it. lib/team-hub.mjs publicMember exposes projectPath to any team member via /api/snapshot, and lib/panel.js renders it in a hover title. Paths such as D:\Work\<client>\<confidential project> therefore leave the machine whenever a team is joined.
Team token-usage tracker: routes are guarded by the DSH trust fence and the panel output is HTML-escaped; no RCE or credential leak, only low hardening gaps.
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-09-25 · activity: Stable
• Repo created: 2026-09-25
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 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 @guooo1380/dsh-team-panel?
@guooo1380/dsh-team-panel 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 @guooo1380/dsh-team-panel?
Run dsh plugin --profile web add github:guooo1380/dsh-team-panel 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.