T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Global Installation of a Third-Party CLI Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Document the authoritative npm publisher, source repository, and expected package metadata so users can verify provenance before installation. 3. Publish and verify an integrity checksum or cryptographic signature for the reviewed package artifact. 4. Prefer a project-local installation with a committed lockfile over a global installation: ```bash npm install --save-exact @coze/cli@ npx coze --version ``` 5. Where compatible, initially acquire the package with lifecycle scripts disabled and inspect it before enabling execution: ```bash npm install --ignore-scripts --save-exact @coze/cli@ ``` 6. Separate package installation and provenance verification from OAuth authentication. Require users to verify the package version and source before providing credentials. 7. Run the CLI under a least-privileged account and grant only the minimum Coze organization, workspace, and project permissions required for the task. 8. Reconcile the GitHub link in `README.md` with the authoritative repository identified by the official Coze documentation. ]]>
