T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Unpinned Global Installation of a Mutable Third-Party Dependency
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected package integrity digest or registry-provided integrity metadata before installation. 3. Document the expected package registry, package namespace, publisher identity, and provenance information. 4. Prefer a project-local installation with a committed lockfile instead of a global installation where operationally possible. 5. Review package lifecycle scripts and consider installation with scripts disabled when they are not required: ```sh npm install --ignore-scripts --save-exact betterprompt@ ``` 6. Run the CLI with a dedicated, least-privileged account or inside a sandbox/container that exposes only required files and credentials. 7. Establish an explicit update process in which new versions are reviewed, verified, and pinned before the documented version is changed. ]]>
