T08 · Insecure Dependencies
- Location
SKILL.md:38- Finding
Unpinned npm Package Is Downloaded and Executed Through npx
- Content
View full analysis
- Remediation
View remediation
"] } } } ``` 2. Install dependencies ahead of execution using a committed lockfile containing package integrity metadata. Use a deterministic installation mechanism such as `npm ci`. 3. Configure runtime execution so it fails if the package is not already installed, preventing `npx` from silently downloading mutable code. 4. Verify package provenance, signatures or attestations where available, and review the selected package version and its transitive dependencies before deployment. 5. Run the MCP server in a sandbox or isolated container with minimal filesystem and network access. 6. Provide only the environment variables required for read-only operation. Do not expose `POLYMARKET_PRIVATE_KEY` unless the operator has explicitly enabled trading. 7. For trading deployments, use a restricted signer or wallet with strict balance, transaction, per-order, and daily spending limits. Separate read-only and trading server profiles. 8. Monitor and approve dependency updates rather than accepting new releases automatically. ]]>
