T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Automatic Retrieval and Execution of an Unverified Third-Party npm Package
- Content
View full analysis
We intentionally avoid global installs (`npm i -g`) to reduce supply-chain risk. > Use a pinned version via `npx` for deterministic behavior. ```bash # Scan current workspace (read-only by default) npx --yes @skillgate/openclaw-skillgate@0.1.3 gov_scan . # Show a human-readable explanation for a finding npx --yes @skillgate/openclaw-skillgate@0.1.3 gov_explain ``` ### Technical Analysis The documented quick-start procedure uses `npx --yes` to retrieve and immediately execute `@skillgate/openclaw-skillgate@0.1.3` from the configured npm registry. The `--yes` option suppresses the normal installation confirmation, reducing the opportunity for the user to inspect the package before execution. Pinning the version improves reproducibility but does not independently authenticate the retrieved artifact. Although the document shows commands for displaying `dist.integrity`, it does not provide a trusted expected integrity value or require verification before execution. The project contains only `SKILL.md`; the source code of the executed npm package is not included. Consequently, the audit cannot verify the claims that scanning is read-only, that secrets are not accessed, or that no network traffic occurs after installation. This finding does not establish that the named package is malicious. It identifies the trust boundary created by downloading and executing unaudited third-party code. ### Attack Path 1. A user follows the Quick Start instructions in `SKILL.md`. 2. `npx --yes` contacts the configured npm registry and downloads the specified package if it is not already available locally. 3. npm lifecycle behavior and the requested CLI entry point execute code supplied by that external package. 4. The ...[truncated 1336 chars]- Remediation
View remediation
