What it may solve
An MC-Fabric-style hook processor.
Imported third-party catalog description; not a Registry verification conclusion.An MC-Fabric-style hook processor.
Author: omdsh-dev · Development & Runtime · Catalog snapshot: 2026-09-19Canonical semantic path
An MC-Fabric-style hook processor.
Imported third-party catalog description; not a Registry verification conclusion.18 stars · 663 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: 19 stars, 132 commits, 1 forks, and 0 watches; latest commit 2026-09-06.
Conclusion: Resolved npm release 0.1.1, published 2026-08-21, license BSD-3-Clause.
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 3 code capabilities: may read environment variables, may create or modify files, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @oh-my-dsh/stent-pack@0.1.1; SHA-256: 46a8b96fadb213ac5ad8935dba5c1c7ecbd30aab13e5d298c72500c78eb8471b.
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 stent. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@oh-my-dsh/stent-packAnalyzed 0.1.1github:omdsh-dev/stentExact version not resolved