T08 · Insecure Dependencies
Warning
- Location
SKILL.md:80- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local development dependency over a global installation, then invoke it through a package script or the local binary. 3. Commit and verify the applicable lockfile so transitive dependency versions are reproducible. 4. Document the expected npm registry and official package source to reduce dependency-confusion and registry-substitution risks. 5. Verify package provenance, signatures, or published integrity metadata before installation. 6. Review lifecycle scripts and consider installation with `--ignore-scripts` when those scripts are not required. 7. Require explicit user approval before installing the package or connecting the workspace to a cloud service. 8. Document what files, credentials, metadata, and network destinations `ritual init` and `ritual status` may access. 9. Run the CLI in a least-privilege or isolated environment when practical. ]]>
