What it may solve
Read the config your harness actually booted, and validate an overlay before you apply it. A Blueprint tab for the DSH web client.
Imported third-party catalog description; not a Registry verification conclusion.Read the config your harness actually booted, and validate an overlay before you apply it. A Blueprint tab for the DSH web client.
Author: taltara · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
Read the config your harness actually booted, and validate an overlay before you apply it. A Blueprint tab for the DSH web client.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 1647 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/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: 2 stars, 51 commits, 0 forks, and 0 watches; latest commit 2026-08-30.
Conclusion: Resolved npm release 0.6.0, published 2026-08-20, 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 observed 2 code capabilities: may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-blueprint@0.6.0; SHA-256: 499e62a9a040e1fb859dec22fe03335cf57265f3cba9e6be45a8e4d3b8b31977.
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-blueprint. 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-blueprintAnalyzed 0.6.0github:taltara/mddl-harnessExact version not resolved