T08 · Insecure Dependencies
- Location
README.md:47- Finding
Unpinned and Unverifiable Third-Party Installation Sources
- Content
View full analysis
Vulnerability Details
File Location:
README.md:47,README.md:53,package.json:23-30
Vulnerability Type: Supply-chain risk through unpinned packages and unverifiable installation sources
Risk Level: MediumVulnerable Code
README.md:47:bash npx skills add yourusername/agent-skills/figma-design-analyzerREADME.md:53:bash git clone https://github.com/yourusername/agent-skills.gitpackage.json:23-30:json "dependencies": { "axios": "^1.6.0", "commander": "^11.1.0", "chalk": "^4.1.2", "dotenv": "^16.3.1", "jsdom": "^22.1.0", "sharp": "^0.33.0" },Technical Analysis
The documented
npxinstallation command does not specify an immutable package version or revision. It may therefore retrieve and execute whichever package version the registry resolves at installation time. The repository URL also uses a placeholder account, preventing users from reliably verifying that they are cloning the intended official source.Runtime dependencies use caret version ranges, while the audited project contains no lockfile. Consequently, separate installations can resolve different dependency versions. This weakens reproducibility and allows the effective dependency code to change after the Skill itself has been reviewed.
This condition does not establish that any current dependency is malicious. It creates a supply-chain exposure in which registry compromise, package-account takeover, namespace confusion, or a malicious future release could introduce executable code without corresponding changes to this repository.
Attack Path
- A user follows the README and executes the unpinned
npxinstallation command or runsnpm install. - The package registry resolves the current package and dependency versions rather than an audited immutable set.
- An attacker who controls or compromises one of the resolved packages publishes a malicious comp ...[truncated 1074 chars]
- A user follows the README and executes the unpinned
- Remediation
View remediation
Remediation Suggestions
- Replace placeholder package and repository identifiers with the verified official project namespace and HTTPS repository URL.
- Pin the documented
npxinstallation to a reviewed exact version or immutable revision. - Pin runtime dependencies to exact versions rather than mutable caret ranges where operationally practical.
- Generate, review, and commit
package-lock.jsonso the complete dependency graph is reproducible. - Use
npm ciin CI/CD and documented production installation procedures. - Review package lifecycle scripts before installation and use
--ignore-scriptswhere lifecycle execution is unnecessary. - Use dependency integrity verification, automated vulnerability scanning, and controlled dependency-update review.
- Run installation and execution with a least-privileged user and avoid exposing unrelated credentials to the process.
