T08 · Insecure Dependencies
- Location
README.md:28- Finding
Recommended Installation Command Executes Unpinned Third-Party Code
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 28-32
Vulnerability Type: T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
markdown ### Opción 1: instalación con `npx` (recomendada) ```bash npx skills add https://github.com/mattc95/Humanizer-es.gittext ### Technical Analysis The recommended installation method invokes the `skills` npm package through `npx` without specifying an exact package version. If the package is not already available locally, `npx` can retrieve and execute the version currently resolved by the configured npm registry. The Git repository supplied to the installer is also referenced through its mutable repository URL rather than an immutable commit. Consequently, neither the installer implementation nor the skill content processed by it is cryptographically or immutably tied to the version reviewed during this audit. This creates a supply-chain trust boundary: future changes to the resolved npm package, compromise of its publisher or registry distribution path, or malicious changes to the repository could cause the documented command to execute behavior that was not present during review. No evidence was found that the current project itself contains a malicious package or payload. The risk arises from recommending execution of mutable, externally controlled dependencies. ### Attack Path 1. An attacker compromises the npm package account, package distribution process, or another component involved in resolving the unpinned `skills` package. 2. Alternatively, an attacker gains control over the referenced Git repository or introduces malicious content into its default branch. 3. A user follows the installation command recommended in `README.md`. 4. `npx` resolves and executes the externally supplied installer package, which then processes content from the mutable Git repository. 5. Malicious installer or repository behavior runs with the permissi ...[truncated 956 chars]- Remediation
View remediation
Remediation Suggestions
-
Pin the
skillsnpm package to a specific, reviewed version instead of relying on the registry's current resolution:bash npx skills@<reviewed-version> add <immutable-source> -
Reference an immutable Git commit rather than the repository's mutable default branch. Document the expected commit hash and verify that the selected installer supports immutable Git references.
-
Publish and document checksums or signed release artifacts so users can verify the downloaded skill before installation.
-
Prefer manual installation as the primary option when feasible. Instruct users to download a tagged release, verify its checksum or signature, inspect the included files, and then copy only
SKILL.mdandREADME.mdinto the destination. -
Document the npm package publisher, expected package version, repository commit, files written during installation, and required permissions.
-
Recommend running the installer in a restricted environment without unnecessary credentials or sensitive environment variables. Users should not run the command with
sudoor an administrator account. -
Re-audit the pinned installer package and repository revision whenever either dependency is updated.
-
