T08 · Insecure Dependencies
- Location
SKILL.md:139- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
- Remediation
View remediation
"], "env": { "LONGFORM_MEMORY_PROJECT": "my-novel" } } } } ``` 2. Install the reviewed version separately through a lockfile-controlled workflow and verify its registry integrity hash. Use `--no-install` at runtime so MCP startup fails rather than downloading unexpected code. 3. Prefer a vendored or locally installed executable whose source, version, and checksum have been reviewed and fixed. 4. Remove `-y` from workflows that may install software automatically, or ensure installation occurs only in an explicit, auditable setup step. 5. Correct the documentation to distinguish runtime behavior from installation behavior. Do not claim “no network” unless package installation and execution are technically prevented from using the network. 6. Run the MCP server with least privilege and restrict its filesystem access to the required memory directory. Avoid exposing unrelated credentials or sensitive environment variables to the process. 7. Establish a dependency update process that reviews release changes and integrity information before changing the pinned version. ]]>
