T08 · Insecure Dependencies
- Location
assets/quick-start.md:7- Finding
Unverified Global Installation of an npm-Compatible CLI Package
- Content
View full analysis
- Remediation
View remediation
dioxus-cli ``` 5. Document the expected registry and official package source so users can detect registry substitution or dependency-confusion conditions. 6. Where the package ecosystem supports it, verify package checksums, signatures, attestations, and publisher identity before installation. 7. Prefer project-local or isolated tool installation over global installation to reduce command-path exposure and limit the scope of a compromised package. 8. Review and pin the other executable installation commands in `SKILL.md`, `assets/project-template.md`, and `assets/quick-start.md` to improve supply-chain reproducibility. ]]>
