T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Global Installation of a Third-Party Executable
- Content
View full analysis
- Remediation
View remediation
``` 2. Record the reviewed package version, source commit, and expected npm integrity digest in the Skill documentation. 3. Verify that the npm artifact corresponds to the reviewed source release before installation. 4. Prefer an isolated, project-local, containerized, or dedicated user-local installation over a global installation. 5. Avoid recommending `sudo npm install -g`; the package should not receive administrator privileges. 6. Where compatible with the package, install with lifecycle scripts disabled: ```bash npm install --ignore-scripts --prefix ~/.local -g taskify-nostr@ ``` If lifecycle scripts are required, review each script before allowing it to run. 7. Re-audit the pinned release and its transitive dependencies whenever the documented version is updated. 8. Require explicit user approval before installation rather than allowing an agent to install or upgrade the package automatically. ]]>
