T08 · Insecure Dependencies
- Location
SKILL.md:299- Finding
Unpinned Third-Party CLI Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:19-28;SKILL.md:299-314
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
README.md:19-28:bash npx skills add ECNU-ICALK/autoskill-skillbash npx skills add ECNU-ICALK/autoskill-skill --skill autoskillSKILL.md:299-314:text 5. When external ecosystem search is requested, duplication risk is high, or the candidate is meant to be public, check well-known sources before creating a new skill. For personal skills, external search is evidence for avoiding duplicates, not a popularity test: - browse `https://skills.sh/` or its leaderboard for popular/battle-tested options - run `npx skills find <query>` with the best 1-2 queries - try alternate terms when the first query misses, e.g. `deploy` vs `deployment` or `pr review` vs `code review` 6. Verify external candidates before recommending them: prefer high install counts, reputable sources, and active source repositories; be cautious with low-install or unknown-author skills. 7. Present external matches with name, purpose, source/quality signal, link, and install command. Do not install, import, overwrite, or merge external skills without explicit user consent.Technical Analysis
The documented commands invoke the
skillsnpm CLI throughnpxwithout pinning a reviewed package version or validating package integrity. If the package is absent from the local cache,npxcan dynamically resolve, download, and execute code from the npm ecosystem.The repository therefore does not completely determine the code executed by these commands. A future package release, compromised maintainer account, registry compromise, dependency confusion event, or malicious transitive dependency could alter the effective executable payload after this skill has been reviewed.
The instruction to verify external skill candida ...[truncated 1625 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
npx skills@X.Y.Z, after confirming the correct package identity and trusted publisher. - Prefer a lockfile-controlled installation with integrity metadata over dynamically resolving a package on every invocation.
- Document the expected npm package name, publisher, source repository, version, and checksum or provenance-verification procedure.
- Require explicit user confirmation before the first invocation of any dynamically downloaded CLI, including discovery-only commands.
- Run the CLI in a restricted environment with minimal filesystem permissions, sanitized environment variables, and no unnecessary credentials.
- Disable lifecycle scripts where compatible with the trusted package workflow, and review the CLI plus its dependency tree before upgrades.
- Separate approval to execute the discovery CLI from approval to install any skill returned by that CLI.
- Pin the CLI to a specifically reviewed version, for example
