T08 · Insecure Dependencies
- Location
skill.json:27- Finding
Unpinned npm Package Is Automatically Retrieved and Executed
- Content
View full analysis
- Remediation
View remediation
", "--http" ] ``` 2. Prefer installing dependencies during a controlled build phase using a committed lockfile and integrity-verified package metadata. Do not dynamically download executable packages when the Skill starts. 3. Remove `-y` where interactive approval is appropriate, although removing it alone does not address mutable dependency resolution. 4. Verify package provenance through registry signatures, trusted publishing, checksums, or an internally controlled package mirror. 5. Pin and audit transitive dependencies. Add automated vulnerability and dependency-drift scanning to the release process. 6. Run the MCP server in a restricted container or sandbox with: - A non-privileged operating-system account. - Read-only filesystem access except for explicitly required paths. - A minimal environment containing only required secrets. - Restricted outbound network access. - Resource limits and no access to host administration interfaces. 7. Scope the UPLO API token to the minimum required operations and institutional datasets. Establish rotation and revocation procedures in case the runtime dependency is compromised. ]]>
