T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Code and Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:15-18andSKILL.md:108-118
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumThe Skill recommends executing mutable npm package versions and installing components or related Skills from remote sources without version pins, immutable commit references, integrity hashes, or signature verification.
Relevant code from
SKILL.md:15-18:bash # Install chat components npx shadcn@latest add https://ui.inference.sh/r/chat.jsonRelevant code from
SKILL.md:108-118:bash # Full agent component (recommended) npx skills add inference-sh/skills@agent-ui # Declarative widgets npx skills add inference-sh/skills@widgets-ui # Markdown rendering npx skills add inference-sh/skills@markdown-uiTechnical Analysis
The
npx shadcn@latestcommand resolves and executes a mutable package version. The remote registry URL also supplies component definitions whose contents can change independently after this Skill has been reviewed. The relatednpx skills addcommands similarly use an unpinned command-line package and mutable Skill references.Because no exact package versions, immutable source revisions, checksums, or signatures are specified, the code ultimately executed or installed may differ from the code originally intended by the Skill author. A compromise of the npm package, remote component registry, associated repository, publisher account, or distribution infrastructure could therefore turn these documented installation commands into a supply-chain delivery mechanism.
No evidence establishes that the currently referenced resources are malicious. The vulnerability is the unsafe reliance on mutable and unverified third-party content.
Attack Path
- An attacker compromises an upstream npm publisher, remote registry, referenced Skill repository, or its distribution infrastructure.
- The attacker publishes ...[truncated 1326 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
shadcn@latestwith an exact, reviewed package version and enforce that version through the package lockfile. - Pin each related Skill to an immutable release or commit hash rather than a mutable repository reference.
- Download and review remote registry manifests and all generated files before adding them to the project.
- Verify downloaded artifacts using trusted checksums or cryptographic signatures where supported.
- Review npm lifecycle scripts and use installation controls that prevent unnecessary script execution.
- Run installation commands in an isolated, least-privileged environment without production credentials or sensitive developer tokens.
- Record approved artifact hashes and periodically audit upstream changes before upgrading.
- Replace
