@kdcadmin/dsh_qzone_sticker avatar

@kdcadmin/dsh_qzone_sticker

给 DeepSeek Harness 用的 QQ 空间插件。它在本机静默起一份专属 Chrome(headless,不占你屏幕),第一次用手机 QQ 扫码登录;之后不用你开浏览器、不用你点按钮——模型可以自己挑时机发说说,还能配上表情包图片,每天发几条、两条隔多久、公开还是仅自己,都能设。

PluginVisionBrowserContentVision / OCR
Verification
L2 · Structured
Risk
Pending
Health
Active
Trust
Bronze

Install verification: No L4/L5 install test yet

Data as of (UTC)

L1–L5 verification rules

What it does

给 DeepSeek Harness 用的 QQ 空间插件。它在本机静默起一份专属 Chrome(headless,不占你屏幕),第一次用手机 QQ 扫码登录;之后不用你开浏览器、不用你点按钮——模型可以自己挑时机发说说,还能配上表情包图片,每天发几条、两条隔多久、公开还是仅自己,都能设。

Installation

dsh plugin --profile web add github:kdcadmin/dsh_qzone_sticker

Install method: GitHub · no verification record (L1-L5)

Verification & Compatibility

No verification record yet for this plugin.

  • • Node.js: not stated
  • • DSH: not stated
  • • External credentials: none detected

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-qzone-sticker.svg)](https://www.dsh.so/artifact/dsh-qzone-sticker/?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-qzone-stickerAutomated review · daily

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

no static verdict→dynamic no conclusion→overall low
static findings0 critical·0 high·— files scanned
lowoverall · low
1static scandeterministic rules · no code execution · shape only
plugin version—
scanned version—
current versionb06f5bcb7245

The scan result is valid for the scanned commit. New commits within 7 days are tolerated (the rating still counts); after 7 days without a rescan the badge shows outdated.

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

• Repo created: 2026-10-28

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/kdcadmin/dsh_qzone_sticker

Frequently asked questions

What is @kdcadmin/dsh_qzone_sticker?

@kdcadmin/dsh_qzone_sticker 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 @kdcadmin/dsh_qzone_sticker?

Run dsh plugin --profile web add github:kdcadmin/dsh_qzone_sticker 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-11-01 (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?