T08 · Insecure Dependencies
Warning
- Location
SKILL.md:53- Finding
Mutable npm Dependency Versions Create Supply-Chain Exposure
- Content
View full analysis
- Remediation
View remediation
", "tailwindcss": "4.0.0", "vite": "8.0.0" } } ``` 2. Generate and commit a reviewed `package-lock.json` so dependency and transitive-dependency resolution is reproducible. 3. Replace the installation instruction with `npm ci`, which installs from the lockfile and rejects manifest-lockfile inconsistencies. 4. Use `npm ci --ignore-scripts` where package functionality permits it. If lifecycle scripts are required, explicitly review and allow only the packages that need them. 5. Enable automated dependency scanning and review dependency updates before refreshing pinned versions or the lockfile. 6. Verify registry configuration and lockfile integrity metadata, and avoid untrusted alternate registries or package sources. 7. Run installation and development commands as an unprivileged user in an isolated development environment without unnecessary credentials or sensitive environment variables. ]]>
