T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Global Installation of an External npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Verify the selected release before recommending it: - Review the package source and npm lifecycle scripts. - Confirm package ownership and provenance. - Record and verify the expected registry integrity digest. - Reassess the package whenever the pinned version is updated. 3. Prefer a project-local installation with a committed lockfile instead of a global installation: ```bash npm install --save-exact meetgeek-cli@ ``` Commit the resulting lockfile so dependency versions and integrity values are reproducible. 4. Disable lifecycle scripts during installation where compatible with the package: ```bash npm install --ignore-scripts --save-exact meetgeek-cli@ ``` 5. Include or vendor the reviewed CLI implementation with the Skill when feasible, allowing its credential handling, external communications, and command execution behavior to be audited together with the wrapper. 6. Execute the CLI with least privilege and restrict access to `~/.config/meetgeek/config.json`, for example by ensuring that only the owning user can read the file. ]]>
