This entry has been merged into: jingbao-voice-pet — verification records were moved there; this page is kept as an archive.

jingbao-pet avatar

jingbao-pet

鲸宝语音桌宠 Jingbao Voice Pet · DSH 桌宠插件(网页版 + 桌面端通用):确认&提问语音播报 + 任务完成闹钟 + CPU/内存/GPU 监测 + DeepSeek 余额 + 音量调节 + 自动更新 + H3 无缝真动画萌娘女仆。Voice alerts for confirmations & questions, task-done alarm, live monitor, balance display, auto-update. Works on DSH Web & Desktop.

PluginDesktopDeveloperBrowserMediaNotificationsWeb search
Verification
L1 · Found
Risk
Out of scope
Health
Stable
Trust
Unrated

Install verification: No L4/L5 install test yetInstall verification details →

Data as of (UTC)

What it doesAI

Desktop pet with voice alerts, system monitoring, and cute animations.

  • Voice alerts for task completion and confirm prompts
  • Real-time CPU, memory, and GPU monitoring
  • Chibi maid pet with animations and voice
desktopAInotificationAI

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 github:windfind-02/jingbao-pet
tested artifact 263b4c1e272657d99bbcefda926290e8b5b979d1

Install method: GitHub · install spec not tested (L3 not tested)

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

Declared DSH compatibilityfrom package.json · peerDependencies
package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
263b4cgithub2026-08-24

https://github.com/windfind-02/jingbao-pet

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/jingbao-pet.svg)](https://www.dsh.so/artifact/jingbao-pet/?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.

jingbao-petAutomated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low
vet findings0 critical·0 high
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin version—
scanned version43e669e5a786git2026-08-26
current version263b4c1e2726version moved on
vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (9)
  • criticalchildProcess · code-execplugin/lib/index.js:13

    import { execFile } from "node:child_process";

  • warningnetIp · networkplugin/lib/client.js:1218

    fetch("http://127.0.0.1:8765/do-update")

  • warningnetIp · networkplugin/lib/client.js:1325

    fetch("http://127.0.0.1:8765/check-update")

  • warningnetIp · networkplugin/lib/client.js:1384

    fetch("http://127.0.0.1:8765/stats")

  • warningshellExec · shellplugin/lib/index.js:175

    execFile("nvidia-smi", ["--query-gpu=utilization.gpu,memory.used,memory.total", "--format=csv,noheader,nounits"], { timeout: 8000 }, (err, s

  • warningnetIp · networkplugin/lib/index.js:249

    console.log("[dsh-pet] 监控服务已启动 http://127.0.0.1:8765/stats");

  • warningfsWrite · filesplugin/lib/index.js:28

    fs.writeFileSync(file, JSON.stringify(obj), { encoding: "utf8" });

  • warningfsWrite · filesplugin/lib/index.js:94

    fs.writeFileSync(dest, buf);

  • warningfsWrite · filesplugin/lib/index.js:233

    fs.writeFileSync(BALANCE_KEY_FILE, String(j.apiKey).trim(), "utf8");

2model reads redacted source context · never executes plugin code

no dynamic conclusion (source harvest or model call failed) — no conclusion is not a pass; the overall rating falls back to the static tier.

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-29 · activity: Stable

• Repo created: 2026-08-17

• Stars: ★ 3 · Forks: 0

• Health: Stable — committed within 90 days

Source

GitHub: github.com/windfind-02/jingbao-pet

Frequently asked questions

What is jingbao-pet?

jingbao-pet 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 jingbao-pet?

Run dsh plugin --profile web add github:windfind-02/jingbao-pet in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest, but its install spec is not verified yet (L3); sandbox install and runtime testing have not passed.

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-10-29 (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.

Was this page helpful?