What it may solve
Injects one system-prompt section that sets how a DeepSeek Harness agent talks, without touching how it reasons
Imported third-party catalog description; not a Registry verification conclusion.Injects one system-prompt section that sets how a DeepSeek Harness agent talks, without touching how it reasons
Author: Max-Null · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Injects one system-prompt section that sets how a DeepSeek Harness agent talks, without touching how it reasons
Imported third-party catalog description; not a Registry verification conclusion.— stars · 0 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 could not be confirmed as reachable.
Conclusion: Resolved npm release 0.1.0, published 2026-09-17, 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 bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @max-null/dsh-tone-layer@0.1.0; SHA-256: e1da10883f769d589d7a1c6c0a6a96cc7cfc2a1e711d1680d8e5ea6eb84bf447.
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 @max-null/dsh-tone-layer. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@max-null/dsh-tone-layerAnalyzed 0.1.0github:Max-Null/dsh-tone-layerExact version not resolved