dsh-code-check
Automatic type-check diagnostics: after the model edits or creates TS files, runs `tsc --noEmit` in the background (debounced per project) and reports errors via the `code_check` tool — grouped by file with line/column, severity and TS error codes, closing the "edit → check → fix" loop.
On this page
Review info: the scan contains items that require human judgment, such as lifecycle scripts, build approval, runtime artifacts or install-documentation issues.
Community signals
Category
Development & Runtime
GitHub stars
1
npm downloads
—
Discovery registry added
2026-08-15
Review information
Scanner status
needs-review
Review mode
guided
Last checked
2026-09-21T12:51:21.444Z
Build approval required
No
Lifecycle scripts
prepare
Runtime artifacts committed
No
Documented profiles
web
readme-documents-github-install-but-runtime-entry-artifacts-are-missing
Why this site does not provide the install command
A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.
Install and usage source
This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.
Minimum checks before install
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.