T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned npm Package May Execute Mutable Remote Code
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Avoid implicit package downloads through an unversioned `npx` command. Install the pinned dependency first and execute the verified local binary, or use: ```bash npx --offline openclaw-video-call ``` after a trusted installation. 3. Distribute and enforce a lockfile with integrity metadata. Use `npm ci` rather than unconstrained installation so dependency resolution is reproducible. 4. Verify package provenance and signatures where supported. Ensure the reviewed source commit, published npm artifact, and documented repository correspond to one another. 5. Audit the runtime and its transitive dependencies before deployment. Add automated dependency scanning and fail installation when integrity or provenance checks do not pass. 6. Run the server with least privilege in a restricted environment: - Provide only the required environment variables. - Restrict filesystem access. - Limit outbound network destinations where practical. - Do not run the package as root or an administrative user. 7. Use a narrowly scoped Runway credential if supported, rotate it regularly, and revoke it immediately if package compromise is suspected. 8. Pin and separately review future updates instead of automatically resolving the latest registry release. ]]>
