All plugins

DSH / BUNDLE / BUNDLES

dsh-stability-audit

v0.13.2chunfenxiazhi-collab / dsh-stability-auditaa4198f13c

InstallableBundlesBundles & other modulesCommunity · Topic auto-analysis

Overview

dsh-stability-audit

Scan installed DeepSeek Harness plugins and grade stability risk (hook surface, startup work, preflight health, packaging, dependencies). 扫描已安装插件的稳定性风险(钩子面/启动任务/预检/打包/依赖)。

README / EN

Package documentation

Registry summary

Scan installed DeepSeek Harness plugins and grade stability risk (hook surface, startup work, preflight health, packaging, dependencies). 扫描已安装插件的稳定性风险(钩子面/启动任务/预检/打包/依赖)。

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

- Static analysis cannot measure runtime behavior (hook throws, real stall duration) — red means "needs a look", not "definitely broken" - Isolated boot uses a headless profile: plugins depending on web-only services (e.g. storageDomain) show ❌ in isolation but may be fine in web — treat as an environment-dependency hint - Runtime probes (event-loop latency, hook timing) are on the v2 roadmap - Fix suggestions are **hints, not auto-applied**: environments differ (junction/overrides fixes depend on the specific mechanism), agents should confirm before executing ### Isolated test vs real environment (what it can and cannot catch) Isolated testing (temp DSH_HOME + headless smoke) answers: **"can this plugin install on its own and boot cleanly?"** — filtering out ~80% of the failure modes (unbuilt entry, missing inject, dependency conflicts, load crashes). | Dimension | Isolated env | Real web profile | Impact | |---|---|---|---| | Services | headless boot | web services + all host services | plugins depending on webServer/webRuntime stay pending in isolation; real behavior not observable | | Co-installed plugins | only the audited one | many plugins interacting | inter-plugin conflicts not caught (hooks stepping on each other, service overrides) | | Config | empty | real config (API keys, models, paths) | config-dependent plugin paths untested | | Credentials/network | no API key | model APIs available | LLM-dependent features only smoke, never execute | | Data | empty storage | real sessions/libraries | data-migration plugins untested | | Runtime duration | seconds of boot smoke | days of residency | setInterval leaks, memory growth not caught | | Permissions/build | same machine, same permissions | same machine, same permissions | ✅ identical | **Suggested usage**: use isolated testing as bulk screening — exclude red/fail targets; for plugins you actually want, install manually and observe. Automatically testing plugins against the real environment is not recommended — plugins have real destructive power (see the dsh-troubleshooting incidents).