T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unpinned Third-Party Packages Installed and Executed from the npm Registry
- Content
View full analysis
- Remediation
View remediation
playwright@ ``` 2. Use a project-local installation instead of `npm install -g`, and invoke the locked binary through a package script or: ```bash npx --no-install playwright install firefox ``` 3. Commit a lockfile generated from reviewed dependencies and use `npm ci` so package resolution is reproducible. 4. Verify registry integrity metadata and review the complete transitive dependency tree before updating versions. 5. Disable lifecycle scripts during installation where compatible: ```bash npm ci --ignore-scripts ``` If scripts are required, audit them explicitly before allowing execution. 6. Run installation and rendering in a restricted, non-privileged environment with minimal filesystem access and no unnecessary credentials. 7. Document the exact supported package versions and establish a controlled process for reviewing and updating them. ]]>
