T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party npm Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
``` 2. Record and verify the expected package integrity digest. Use a lockfile or an equivalent reproducible dependency manifest where the installation environment supports it. 3. Prefer a project-local installation over a global installation: ```bash npm install --save-exact @shan8851/fuel-cli@ ``` Invoke it through a controlled project script or a locally resolved binary rather than adding it globally to the user's command path. 4. Publish or vendor the corresponding reviewed source code so that credential handling, outbound requests, cache permissions, command parsing, and npm lifecycle scripts can be audited. 5. Disable npm lifecycle scripts during installation when they are not required: ```bash npm install --ignore-scripts --save-exact @shan8851/fuel-cli@ ``` 6. Run the CLI with least privilege and expose credentials only to the specific process that requires them. Do not install or invoke it as an administrator unless independently justified. 7. Restrict `FUEL_FINDER_BASE_URL` to approved HTTPS endpoints in the implementation so OAuth credentials cannot be accidentally transmitted to an untrusted host. 8. Establish a dependency update process in which new package versions and their integrity values are reviewed before the pinned version is changed. ]]>
