T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Third-Party Packages and Browser Extension Create Supply-Chain Exposure
- Content
View full analysis
- Remediation
View remediation
"] } ``` 2. Prefer a locally installed, reviewed package over downloading executable code during each MCP launch. 3. Publish expected package integrity hashes and verify downloaded artifacts before execution. 4. For source installations: - Reference an immutable commit hash or signed release tag. - Verify the release signature or published checksum. - Commit a reviewed lockfile. - Use `npm ci` rather than unconstrained `npm install`. - Review package lifecycle scripts before installation. 5. Link to one exact extension-store listing and document its publisher identity, reviewed version, permissions, and expected checksum where the distribution platform supports verification. 6. Pin the extension to a reviewed release and document an update-review process. 7. Run the MCP server with a restricted OS account or sandbox that cannot access unrelated files, credentials, or services. 8. Limit browser extension host permissions to the minimum OpenTable origins required for operation. ]]>
