T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Package and Repository Code Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Record and verify the expected package integrity digest before installation. Publish the verified package version and checksum in the Skill documentation. 3. For source installation, pin a full reviewed commit hash: ```bash git clone https://github.com/cyberash-dev/claude-usage-cli.git cd claude-usage-cli git checkout --detach ``` 4. Include and enforce a lockfile for reproducible transitive dependency resolution. Prefer `npm ci` over an unconstrained `npm install`. 5. Review npm lifecycle scripts and dependencies before installation. Use `--ignore-scripts` when lifecycle scripts are unnecessary, and run any required build step separately only after inspection. 6. Avoid global installation where possible. Install into an isolated, least-privileged environment and invoke the pinned executable through an explicit path. 7. Vendor the reviewed implementation into the audited artifact, or provide signed release artifacts with provenance attestations so the installed code can be tied to the reviewed source. 8. Update the Skill's deprecated installation metadata so automated installers do not continue installing an unmaintained and unpinned package. Prefer the actively maintained replacement only after applying the same version-pinning and integrity-verification controls. ]]>
