T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Execution of a Third-Party npm Package Without Artifact Integrity Verification
- Content
View full analysis
``` ```bash npm install -g @dlazy/cli@1.2.0 ``` Equivalent installation instructions are present in `SKILL-cn.md`. ### Technical Analysis Both installation methods retrieve executable package content from the npm registry and run it with the permissions of the invoking user. Pinning the dependency to version `1.2.0` reduces unintended version drift, but it does not authenticate the contents of the downloaded artifact or establish that the published npm package corresponds to the linked source repository. The Skill does not provide or validate an integrity digest for the reviewed package artifact. It also does not restrict npm lifecycle scripts. Consequently, installation can execute lifecycle hooks supplied by the package before the primary CLI command is invoked. The global installation path persists the CLI on the user's system beyond the individual Skill invocation. The `npx` path avoids a permanent global installation but still downloads and executes registry-delivered code. There is also a provenance inconsistency: the documentation states that the installation specification pins `@dlazy/cli` to version `1.0.9`, while the metadata and executable installation commands use version `1.2.0`. This discrepancy can undermine source and artifact review by leaving ambiguity about which version was actually assessed. No evidence in the audited files establishes that the current package release is malicious. The vulnerability is the unverified trust and execution model surr ...[truncated 1790 chars]- Remediation
View remediation
