@Firefly26710Lover/dsh-firefly-pet avatar

@Firefly26710Lover/dsh-firefly-pet

流萤桌宠:透明置顶的 DSH 桌面伴侣,能聊天、会碎碎念、播报任务进度 / Firefly desktop pet for DeepSeek Harness

PluginDesktopAutomation
Verification
L4 · Install tested
Failed
Risk
LowRisk
Health
Active
Trust
Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →

Data as of (UTC)

What it does

流萤桌宠:透明置顶的 DSH 桌面伴侣,能聊天、会碎碎念、播报任务进度 / Firefly desktop pet for DeepSeek Harness

Installation

dsh plugin --profile web add github:Firefly26710Lover/dsh-firefly-pet
verified

Install 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

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

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.1-rc.3
current
6f16ca✗
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
6f16cagithub1 failed2026-10-29

https://github.com/Firefly26710Lover/dsh-firefly-pet

✗dsh 0.2.1-rc.3current2026-10-29L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.3
  • • Plugin artifact: github · https://github.com/Firefly26710Lover/dsh-firefly-pet (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-firefly-pet@6f16ca@dsh0.2.1-rc.3 · profile: l4-sandbox

Issued: 2026-10-29 · expires: 2026-11-05

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-29
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-29
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-29
spec github:Firefly26710Lover/dsh-firefly-pet · channel GitHub source · outcome ran · exit 0
check took: 19.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-29
spec github:Firefly26710Lover/dsh-firefly-pet · channel GitHub source · outcome ran · exit 0
check took: 19.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-29
spec github:Firefly26710Lover/dsh-firefly-pet · channel GitHub source · outcome ran · exit 0
check took: 19.1s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-29
spec github:Firefly26710Lover/dsh-firefly-pet · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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:

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

dsh-firefly-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 versionv0.1.0dsh manifest
scanned version0.1.0npm2026-10-29
current version0.1.0same version
vet verdictclean · npm

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

show static findings (3)
  • warningchildProcess · code-execlib/index.js:207

    const child = spawn(electron, [HELPER_MAIN], {

  • warningfsWrite · filesruntime/helper/main.cjs:26

    fs.appendFileSync(LOG_FILE, line, 'utf8')

  • warningfsWrite · filesruntime/helper/main.cjs:299

    fs.writeFileSync(POSITION_FILE, JSON.stringify({ x, y }), 'utf8')

2model reads redacted source context · never executes plugin code

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

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

• Repo created: 2026-10-29

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/Firefly26710Lover/dsh-firefly-pet

Frequently asked questions

What is @Firefly26710Lover/dsh-firefly-pet?

@Firefly26710Lover/dsh-firefly-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 @Firefly26710Lover/dsh-firefly-pet?

Run dsh plugin --profile web add dsh-firefly-pet 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-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?