What it may solve
Automated acceptance testing for DeepSeek Harness plugins: declarative scenarios, isolated runs, assertions and LLM judging.
Imported third-party catalog description; not a Registry verification conclusion.Automated acceptance testing for DeepSeek Harness plugins: declarative scenarios, isolated runs, assertions and LLM judging.
Author: Flan246 · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Automated acceptance testing for DeepSeek Harness plugins: declarative scenarios, isolated runs, assertions and LLM judging.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 26 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 4/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 0 stars, 16 commits, 0 forks, and 0 watches; latest commit 2026-09-09.
Conclusion: Resolved npm release 0.1.0, published 2026-09-08, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan found 6 characteristics that need attention: contains credential or token handling code, may read environment variables, may create or modify files, may access the network, may start external processes, may execute shell commands. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-plugin-litmus@0.1.0; SHA-256: 4c233e701c1214debab41af1266fd28c6d9987094d147bc0d838836b0cd0d225.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-plugin-litmus. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-plugin-litmusAnalyzed 0.1.0github:Flan246/dsh-plugin-litmusExact version not resolved