T08 · Insecure Dependencies
- Location
SKILL.md:48- Finding
Unpinned Playwright MCP Dependency Allows Execution of Unreviewed Upstream Code
- Content
View full analysis
- Remediation
View remediation
"] ``` 2. Manage the dependency in a package manifest and lockfile rather than resolving it dynamically whenever the MCP server starts. 3. Commit and review the lockfile, and use a clean installation mechanism such as `npm ci` that honors locked dependency versions and integrity hashes. 4. Configure the package manager to use a trusted registry and preserve package integrity verification. 5. Review release notes and dependency changes before upgrading the pinned version. Perform upgrades through explicit, controlled change requests rather than automatic tag resolution. 6. Run the MCP server under a dedicated, least-privileged account or sandbox with restricted filesystem, environment-variable, and network access. 7. Avoid exposing unrelated credentials or sensitive local directories to the MCP process. 8. Where operationally feasible, disable package lifecycle scripts during installation and obtain the dependency from an internally approved or verified artifact repository. ]]>
