@MoonLoordSaMa/dsh-starr avatar

@MoonLoordSaMa/dsh-starr

基于snowluma & onebot协议,面向DSH 的 AI bot养成插件,连接 QQ 与 B站,整合角色人设、情绪驱动、跨平台共享记忆、Obsidian 双向链接记忆库与听说看唱能力,配备沉浸式三维记忆星图和网页控制台

PluginAI ModelsBrowserKnowledgeMemoryVision / OCR
Verification
L3 · Install spec
Risk
LowRisk
Health
Active
Trust
Silver

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

Data as of (UTC)

What it doesAI

AI companion bot linking QQ and Bilibili with persona, emotion-driven chat, shared Obsidian-style memory, voice/singing skills and a 3D memory star map.

  • Connects QQ and Bilibili, sharing one cross-platform bot persona
  • Emotion-driven replies backed by an Obsidian-style linked memory vault
  • Hearing, speaking and singing skills plus a 3D memory star-map web console
aiAImemoryAIvisionAI

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:MoonLoordSaMa/dsh-starr
verified

Install method: GitHub · install spec verified (L3)

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
v0.2.4github2026-11-10

https://github.com/MoonLoordSaMa/dsh-starr

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

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:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-starr.svg)](https://www.dsh.so/artifact/dsh-starr/?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-starrAutomated 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.2.4dsh manifest
scanned versionv0.2.4git2026-11-11
current versionv0.2.4same version
vet verdictclean · git

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

show static findings (2)
  • warningnetIp · networkscripts/browser-open.js:1

    await page.goto("http://127.0.0.1:17841/", { waitUntil: "networkidle" });

  • warningnetIp · networkvite.config.ts:8

    server: { proxy: { "/api": "http://127.0.0.1:17841" } },

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-11-07 · activity: Active

• Repo created: 2026-11-04

• Stars: ★ 3 · Forks: 1

• Health: Active — committed within last 30 days

Source

GitHub: github.com/MoonLoordSaMa/dsh-starr

Frequently asked questions

What is @MoonLoordSaMa/dsh-starr?

@MoonLoordSaMa/dsh-starr 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 @MoonLoordSaMa/dsh-starr?

Run dsh plugin --profile web add github:MoonLoordSaMa/dsh-starr#v0.2.4 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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-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.

Was this page helpful?