T08 · Insecure Dependencies
- Location
SKILL.md:61- Finding
Unpinned npm Packages Are Downloaded and Executed
- Content
View full analysis
- Remediation
View remediation
npx --yes @social0/mcp@ ``` 2. Replace placeholders with an exact version only after verifying the release; do not use version ranges or tags such as `latest`. 3. For managed deployments, use a lockfile and `npm ci` to obtain deterministic dependency resolution. 4. Verify package provenance, publisher identity, release signatures where available, and registry integrity metadata before execution. 5. Disable or review npm lifecycle scripts when they are not required. 6. Avoid global installation where possible. Execute the dependency in a constrained environment with only the minimum required filesystem, network, and credential access. 7. Establish an update process in which new versions are audited before changing the pinned version. ]]>
