T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Global Installation of a Third-Party Browser Automation Dependency
- Content
View full analysis
- Remediation
View remediation
``` 2. Install it as a project-local dependency rather than globally. 3. Commit and enforce a lockfile containing npm integrity hashes. 4. Use `npm ci` in automated environments to prevent unreviewed dependency resolution changes. 5. Verify and document the package publisher, registry, expected browser component source, and component checksums. 6. Review lifecycle scripts before installation and consider initially installing with: ```bash npm ci --ignore-scripts ``` 7. Execute the browser tooling in a sandbox or container with access limited to the files and network destinations required for Douyin searches. ]]>
