T08 · Insecure Dependencies
Error
- Location
SKILL.md:18- Finding
Mutable Playwright MCP Dependency Is Automatically Downloaded and Executed
- Content
View full analysis
- Remediation
View remediation
--headless --isolated ``` Do not use version ranges, mutable tags, or unspecified versions. 2. Prefer installing dependencies through a committed lockfile with integrity metadata rather than fetching them dynamically during each skill invocation. 3. Where practical, install the reviewed package during a controlled setup phase and execute the locally installed binary afterward. Runtime operation should not implicitly download new code. 4. Update `scripts/validate.sh` to reject mutable references such as `@latest` and require the approved exact version. The validation should also ensure that every documented invocation uses the same pinned version. 5. Introduce an explicit dependency-update process that includes: - Review of upstream release notes and source changes. - Package provenance and publisher verification. - Lockfile and integrity-hash updates. - Security testing before changing the approved version. 6. Protect shared browser profiles with restrictive filesystem permissions and avoid exposing persistent authenticated profiles to newly updated or unreviewed dependency versions. 7. Consider running browser automation in a sandbox or isolated account with minimal filesystem access, restricted environment variables, and controlled network access to reduce the impact of a compromised dependency. ]]>