Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
An idea incubator that records your pain points and ideas.
- Captures ideas and pain points
- Local-first design
- Cowboy-themed camp experience
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:pakco77/dsh-daqi.skillInstall method: GitHub · runtime test inconclusive (L5 unknown)
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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
11 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-16 · 11 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-28 → 11-16 · 10 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 870dd2 | ○ | · | · | · | · |
| 7c809e | · | · | · | · | · |
| 257110 | · | ○ | ○ | ○ | ○ |
870dd2github○ 1 ecosystem plugin2026-11-16
https://github.com/pakco77/dsh-daqi.skill
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill#870dd217595ce401d1aab774a34fa4d40e6d3fc1
ID: dsh-daqi-skill@870dd217595ce401d1aab774a34fa4d40e6d3fc1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
7c809egithub○ 1 ecosystem plugin2026-09-04
github:pakco77/dsh-daqi.skill
○dsh 0.1.2-rc.12026-09-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:pakco77/dsh-daqi.skill#7c809e
ID: dsh-daqi-skill@7c809e@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
257110github○ 15 ecosystem plugin2026-11-05
https://github.com/pakco77/dsh-daqi.skill
○dsh 0.2.2-rc.12026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.5-rc.22026-09-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.22026-09-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-alpha.12026-09-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-daqi-skill@257110@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/pakco77/dsh-daqi.skill (version unstated)
ID: dsh-daqi-skill@257110@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-daqi-skill@870dd2…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
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-daqi-skill/?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.
Static low; dynamic medium (authoritative when present) → overall medium.
—870dd217595cgit2026-11-17870dd217595csame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningnetIp · network
skills/daqi/scripts/camp_bridge.py:237print(f"daqi bridge: http://127.0.0.1:{args.port} → {config_path(Handler.store)}") - warningnetIp · network
skills/daqi/scripts/camp_status.py:980fetch('http://127.0.0.1:8799/delete', { - warningnetIp · network
skills/daqi/scripts/camp_status.py:1075fetch('http://127.0.0.1:8799/deep-dive', { - warningnetIp · network
skills/daqi/scripts/camp_status.py:1267fetch('http://127.0.0.1:8799' + path, {
show 4 audit findings
- mediumLoopback bridge has no Origin/token check and replies with Access-Control-Allow-Origin: * to all mutating routes
skills/daqi/scripts/camp_bridge.py:30Handler.do_POST routes /ping, /delete, /deep-dive, /scan, /scan-commit and /set-key with no authentication, no Origin/Host validation, and a wildcard CORS header (also sent from do_OPTIONS). While the user has run the bridge (the normal way to use the settings panel), any page the user visits can, subject to browser private-network policies, overwrite ~/.daqi/config.json's api_key (locking the user out or substituting another key), delete lines from POOL.md/SHELF.md, and start scans that spend the user's key; /ping additionally leaks the store path and whether a key is configured.
- medium/deep-dive reads context files from an arbitrary filesystem path and returns their snippets to the caller
skills/daqi/scripts/camp_bridge.py:200The path is taken verbatim from the JSON body (only an is_dir check), so /deep-dive will walk any directory and return the first line of NOW.md / README.md / SKILL.md / docs/*.md content inside the response text, which carries Access-Control-Allow-Origin: *. Any web page (or a local file:// page) can therefore use the bridge as a limited local file-read oracle for arbitrary directories, and the same content is additionally shipped to the configured remote LLM endpoint, turning the bridge into an exfiltration channel.
- mediumUntrusted project file contents are piped into a local codex/claude CLI running with cwd=$HOME
skills/daqi/scripts/camp_scan.py:289When no LLM api_key is configured and a deep scan is requested, call_agent_brain feeds the raw text of context files (README.md / SKILL.md / docs from any workspace found in session history, including freshly cloned third-party repos) into an autonomous agent CLI with no sandbox or approval flags, in the user's home directory and with a 10-minute timeout. A malicious README can prompt-inject the agent, which runs with the user's privileges; this path is also reachable through the unauthenticated bridge's /scan route.
- lowcamp_now_fill --commit writes NOW.md to any path supplied in the proposals JSON, not only SHELF entries
skills/daqi/scripts/camp_now_fill.py:116The commit loop trusts candidates read from an arbitrary --proposals file and never checks c['path'] against the SHELF/missing_now list, so a proposals file produced from untrusted project content (or edited by hand) can create 00_Context/NOW.md directories/files outside the camp store. Content is limited to the four generated fields and a token confirmation is required, which caps the impact.
Unauthenticated CORS-wildcard loopback bridge allows cross-site key writes, deletes and arbitrary-directory /deep-dive reads; untrusted repo text is fed to a local codex/claude agent.
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-08-15 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 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 dsh-daqi.skill?
dsh-daqi.skill is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 dsh-daqi.skill?
Run dsh plugin --profile web add github:pakco77/dsh-daqi.skill in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-17 (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.
