T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Third-Party SDK Dependency
- Content
View full analysis
- Remediation
View remediation
``` 2. Commit a reviewed `package-lock.json` containing dependency versions and integrity hashes. 3. Use `npm ci` in automated or reproducible environments so installation fails when the manifest and lockfile disagree. 4. Review direct and transitive dependency changes before upgrades, and use automated vulnerability and provenance checks. 5. Where operationally compatible, disable package lifecycle scripts during installation: ```bash npm ci --ignore-scripts ``` 6. Run dependency installation and transaction tooling with least privilege, isolated from unrelated credentials and sensitive files. 7. Document a controlled update process that verifies package ownership, release provenance, checksums or npm integrity metadata, and security advisories before changing the pinned version. ]]>
