What it may solve
Bottom multi-tab terminal panel (node-pty + xterm.js) pinned to the viewport bottom, always below the input box.
Imported third-party catalog description; not a Registry verification conclusion.Bottom multi-tab terminal panel (node-pty + xterm.js) pinned to the viewport bottom, always below the input box.
Author: siberiah2o · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
Bottom multi-tab terminal panel (node-pty + xterm.js) pinned to the viewport bottom, always below the input box.
Imported third-party catalog description; not a Registry verification conclusion.siberiah2o/dsh-plugin-terminal
7 stars · 902 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: 6 stars, 28 commits, 3 forks, and 0 watches; latest commit 2026-08-19.
Conclusion: Resolved npm release 0.2.0, published 2026-08-19, license MIT.
Conclusion: Compatibility verification did not pass: the DSH process exited because the plugin imports an API that this DSH version does not export. 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 5 characteristics that need attention: 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-terminal@0.2.0; SHA-256: e200f262316b26b5b0db836017f9fe5f574b82e59a172f7ede497be529e3798d.
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-terminal. 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-terminalAnalyzed 0.2.0github:siberiah2o/dsh-plugin-terminalExact version not resolved