T08 · Insecure Dependencies
- Location
SKILL.md:43- Finding
Unpinned Third-Party npm Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Generate, review, and commit `package-lock.json` so direct and transitive dependency versions are reproducible. 3. Use deterministic installation in established repositories: ```bash npm ci ``` 4. Remove the `npm install zenn-cli@latest` recommendation. Replace it with a controlled upgrade procedure that: - Selects an explicit version. - Reviews release notes and dependency changes. - Verifies package identity and provenance. - Runs vulnerability and integrity checks. - Tests the upgrade in an isolated environment before adoption. 5. Where supported, verify npm package provenance and registry integrity metadata before installation. 6. Run dependency installation and preview commands in a restricted container or sandbox without production secrets, unnecessary credentials, or broad host filesystem access. 7. Avoid running npm as an administrator or root user, and expose only the repository directories required for the Zenn workflow. ]]>
