What it may solve
Model-based permission approval: an approval-request answerer backed by a separate reviewer model.
Imported third-party catalog description; not a Registry verification conclusion.Model-based permission approval: an approval-request answerer backed by a separate reviewer model.
Author: Letter2025 · Security & Permissions · Catalog snapshot: 2026-09-19Canonical semantic path
Model-based permission approval: an approval-request answerer backed by a separate reviewer model.
Imported third-party catalog description; not a Registry verification conclusion.7 stars · 806 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure has not been analyzed.
Repository metadata has not been analyzed.
npm release metadata has not been analyzed.
Installation and startup verification has not been run.
Dependency audit has not been run.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The static risk scan could not complete because package validation did not pass.
Conclusion: Core package structure passed, but an optional export path is missing.
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-approval-llm. 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-approval-llmAnalyzed 0.1.6github:Letter2025/dsh-approval-llmExact version not resolved