T08 · Insecure Dependencies
- Location
README.md:29- Finding
Unpinned Third-Party Installer and Mutable Repository References
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 29-42
Vulnerability Type: Supply-chain risk caused by unpinned installer and repository dependencies
Risk Level: MediumVulnerable Code
bash npx skills add tmchow/agent-skills --skill vhs-terminal-recorderbash npx skills add tmchow/agent-skills --skill vhs-terminal-recorder --globalbash hermes skills install tmchow/agent-skills/vhs-terminal-recorderTechnical Analysis
The documented installation commands do not pin the
skillsnpm CLI to an exact reviewed version and retrieve the skill through mutable repository references rather than a verified commit or immutable release artifact.Consequently, the software installed or executed when a user follows these instructions can differ from the content reviewed during this audit. This creates a time-of-check/time-of-use supply-chain gap. The audited files contain no evidence that the current dependencies are malicious; the risk arises because a future compromise or unauthorized upstream change could alter the effective installation payload.
In particular,
npxmay download and execute a package when it is not already installed locally. Without an explicit version and integrity verification, execution depends on the package currently resolved by the registry. Similarly, repository-based skill installation can resolve to mutable upstream content unless the installer independently enforces immutable revisions.Attack Path
- An attacker compromises the npm package, its publisher account, the source repository, or another relevant upstream distribution channel.
- The attacker publishes a malicious version of the installer or modifies the repository content resolved by the unpinned reference.
- A user follows one of the documented installation commands.
- The package manager or skill installer retrieves the attacker-controlled version instead of the content rev ...[truncated 1016 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm CLI to an exact reviewed version, for example by using an explicit version in the
npxpackage specification. - Pin repository installations to a verified commit hash or immutable, signed release tag where supported.
- Prefer release artifacts with published SHA-256 checksums or cryptographic signatures, and document the verification procedure.
- Use package-manager lockfiles and integrity metadata where installation occurs through a managed project.
- Avoid recommending global installation by default. Prefer project-scoped installation to limit the blast radius.
- Document the upstream sources that users should expect the installer to contact and advise users to review material changes before upgrading.
- If the relevant skill managers do not support immutable references, explicitly disclose that limitation and provide a manual installation workflow tied to a verified commit.
- Pin the npm CLI to an exact reviewed version, for example by using an explicit version in the
