T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned npm Plugin Allows Mutable Supply-Chain Code Execution
- Content
View full analysis
- Remediation
View remediation
" ``` ```bash openclaw plugins install @nutrient-sdk/nutrient-openclaw@ ``` 2. Verify package provenance and integrity before installation. Where supported, require an immutable package digest, npm integrity value, signed provenance statement, or equivalent artifact attestation. 3. Commit and enforce a lockfile if the OpenClaw installation mechanism supports one. Avoid version ranges and floating tags. 4. Review the installed package source and transitive dependency tree for each upgrade. Use dependency scanning and require deliberate approval before changing the pinned version. 5. Run the plugin with least privilege: - Restrict filesystem and environment-variable access. - Expose only the required API credential. - Limit outbound network access to documented Nutrient endpoints. - Use a dedicated, revocable API key with the minimum available permissions. - Isolate document processing from unrelated sensitive host resources. 6. Document the audited package version and its integrity information in the Skill so users can verify they are installing the reviewed artifact. ]]>
