T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned npm Package Installation and Remote Execution Through npx
- Content
View full analysis
Vulnerability Details
File Locations:
SKILL.md:16-20SKILL.md:108-113README.md:12-16
Vulnerability Type: Unpinned third-party dependency and mutable remote package execution
Risk Level: MediumVulnerable Code:
SKILL.md:16-20:yaml install: # Install the CapForge CLI through a fixed dependency and avoid npx remote execution - kind: node package: capforge bins: [capforge]SKILL.md:108-113:bash ### Step 3) Generate transform-plan.md ```bash npx capforge transform <project-name>text `README.md:12-16`: ```bash # Import and scan npx capforge import https://github.com/nousresearch/hermes-agent npx capforge scan hermes-agent npx capforge describe hermes-agentTechnical Analysis
The Skill declares the
capforgenpm package without an exact version or integrity constraint. It also directs users or Agents to invoke the package throughnpx capforge.When the package is not already available locally,
npxcan retrieve the currently published package from the configured npm registry and execute it. The effective code therefore may change after the Skill has been reviewed. A compromised maintainer account, malicious package release, registry compromise, or unexpected future version could introduce arbitrary code without any modification to this Skill package.This behavior also conflicts with the comment in
SKILL.md:17, which claims that the dependency is fixed and that remote execution throughnpxis avoided. The declared installation is not fixed becausepackage: capforgecontains no version, and multiple documented commands explicitly usenpx.The repository pre-scan warning concerning
curl | shis not itself a vulnerability. The occurrence inSKILL.md:35is explanatory text that prohibits such execution rather than an executable command.Attack Path
- An attacker compromises the npm publishe ...[truncated 1491 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin
capforgeto a reviewed exact version in the Skill metadata, for example:yaml package: capforge@1.3.3Confirm the exact syntax supported by the Skill installer before publishing.
-
Replace every
npx capforge ...instruction with the already-declared installed binary:bash capforge transform <project-name> capforge import https://github.com/nousresearch/hermes-agent capforge scan hermes-agent capforge describe hermes-agent -
Use a lockfile and npm integrity hashes wherever the installation framework supports them.
-
Review the pinned package contents, transitive dependencies, executable entry points, and npm lifecycle scripts before approving an update.
-
Disable lifecycle scripts during installation when they are not required, such as through
npm install --ignore-scripts, subject to compatibility testing. -
Ensure upgrades require an explicit security review rather than automatically tracking the latest registry release.
-
Update the documentation so its security claims accurately reflect the implemented installation and execution process.
-
