T08 · Insecure Dependencies
- Location
SKILL.md:11- Finding
Unpinned Global Third-Party Dependency
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local installation over a global installation and invoke the pinned binary from that controlled environment. 3. Commit and enforce a lockfile where the deployment model permits it, using deterministic installation such as `npm ci`. 4. Verify package provenance and integrity before deployment, including the publisher, package metadata, release history, and registry integrity hash. 5. Review dependency changes before upgrading and use automated supply-chain scanning for the package and its transitive dependencies. 6. Disable npm lifecycle scripts during installation where compatible: ```bash npm install --ignore-scripts yahoo-finance2@ ``` 7. Run the CLI under a dedicated, least-privileged account or sandbox with restricted filesystem and network access. 8. Document a tested version and controlled upgrade process in `SKILL.md` rather than directing users to install the latest available release. ]]>
