T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Remote Dependency Installation Allows Supply-Chain Code Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish immutable, versioned releases and document the exact supported release and commit. 3. Provide cryptographic checksums or signed release artifacts, and require users to verify them before installation. 4. Commit and review an npm lockfile in the upstream project. Use deterministic installation: ```bash npm ci ``` 5. Audit direct and transitive dependencies, including all npm lifecycle scripts, before approving a version. 6. Where operationally possible, initially install dependencies with lifecycle scripts disabled: ```bash npm ci --ignore-scripts ``` Run only specifically reviewed build steps afterward. This option must be tested because some legitimate dependencies may require installation scripts. 7. Perform installation and builds in a sandbox, container, or dedicated low-privilege account without access to production credentials or sensitive user files. 8. Avoid exposing `RUNNINGHUB_API_KEY` or other secrets to dependency installation and build processes unless strictly required. 9. Update both `SKILL.md` and `README.md` so that all installation examples consistently use the same pinned and verified version. ]]>
