SD-011 — Vulnerable Dependencies
SD-011 flags specific pip, npm and go installation-from-URL forms and raw GitHub script references in supported files; it does not consult advisories.
What it matches
pip, npm or go installation from specific URL/git forms, or a raw.githubusercontent.com script reference. The rule does not query advisories or flag every unpinned dependency.
Why it matters
A URL, moving git reference or raw-file link can resolve to different content later or for another caller. If installation occurs, the executed dependency may differ from what a reviewer saw. The rule does not resolve the source, inspect package contents or query vulnerability databases.
Example
bash
# Setup in SKILL.md: pip install https://files.example.com/packages/helper-0.1.tar.gz npm install github:example-org/helper-tool
Neither install names a registry package and a version, so neither resolves to fixed bytes.
How to fix it
Install by package name with an exact version from the language's registry, and commit a lockfile so a repeat install produces the same bytes. Where a fork or a patch is genuinely needed, publish it to the registry, or pin the git reference to an immutable commit SHA rather than a branch.
Known false positives
A first-party URL or internal git host used deliberately. The line alone cannot establish trust.
Standards mapping
Prevalence
Pattern SD-011 was detected in 138 of 16996 public skills scanned as of 27 October 2026.
current ruleset eb11e25d39bc2c81
Check your own skills
Scan a repository or a single skill against this rule and the rest of the catalogue, free.