What it may solve
Pre-install supply-chain poison scanner for DSH plugins: AST (JS-X-Ray) + deobfuscation + regex heuristics, exits non-zero on findings for CI gating.
Imported third-party catalog description; not a Registry verification conclusion.dsh-poison-guard
Automated evidence availablePre-install supply-chain poison scanner for DSH plugins: AST (JS-X-Ray) + deobfuscation + regex heuristics, exits non-zero on findings for CI gating.
Author: zoahdev · Security & Permissions · Catalog snapshot: 2026-09-19Canonical semantic path
Security, Permissions & GovernancePlugin & Supply-Chain Security Audit
One primary path; alternate capabilities remain separate.Sources and public signals
1 stars · 569 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19What can currently be confirmed
Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Source structure
Conclusion: The source structure check completed without finding a structural issue.
Repository health
Conclusion: The GitHub repository is reachable and not archived. Public data: 2 stars, 36 commits, 0 forks, and 0 watches; latest commit 2026-08-17.
npm release
Conclusion: Resolved npm release 0.2.0, published 2026-08-16, license MIT.
DSH compatibility
Conclusion: Compatibility verification did not pass: the DSH process exited because a runtime dependency could not be loaded. Test environment: DSH 0.1.6-alpha.2, web profile.
Dependency audit
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
Functional verification
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Static risk scan
Conclusion: The scan found 6 characteristics that need attention: declares a prepare script, normally used when building or publishing the package, contains credential or token handling code, may execute dynamically constructed code, may read environment variables, may access the network, may start external processes. This is a bounded automated observation, not a determination of malicious intent.
Package integrity
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-poison-guard@0.2.0; SHA-256: b190f9a96464c6324e968024561d5fff3364f33d784fbba96ef94c705ceb6b5c.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Continue with the latest plugin manager
Describe your task in a DSH conversation and mention dsh-poison-guard. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
Sources available for local inspection
- npm package
dsh-poison-guardAnalyzed 0.2.0 - GitHub source
github:zoahdev/dsh-poison-guardExact version not resolved