OR

orbit-sec-supply-chain

Audits your dependencies for vulnerabilities, license compliance, and security risks.

Install

mkdir -p .claude/skills/orbit-sec-supply-chain && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14330" && unzip -o skill.zip -d .claude/skills/orbit-sec-supply-chain && rm skill.zip

Installs to .claude/skills/orbit-sec-supply-chain

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Supply-chain security audit — Composer + npm dependency CVE check, license compatibility (GPL-compatible only), abandoned package detection, typosquatting risk, lockfile integrity, post-install / preinstall scripts that smell like supply-chain attacks. Use when the user says "supply chain audit", "dependency CVE", "composer audit", "npm audit", "vendor security".
365 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Check for known CVEs in Composer dependencies
  • Check for known CVEs in npm dependencies
  • Verify license compatibility (GPL-compatible only for WP plugins)
  • Detect abandoned packages
  • Identify typosquatting risk
  • Audit lockfile integrity

How it works

The skill audits Composer and npm dependencies for CVEs, license compatibility, abandoned packages, typosquatting, and lockfile integrity by running various audit commands and cross-referencing security databases.

Inputs & outputs

You give it
A plugin directory with Composer and/or npm dependencies
You get back
A markdown report detailing supply chain audit findings and recommendations

When to use orbit-sec-supply-chain

  • Performing dependency security audits
  • Checking for GPL license compliance
  • Identifying abandoned packages in node_modules

About this skill

🪐 orbit-sec-supply-chain — Dependency supply-chain audit

A plugin is only as secure as its weakest dependency. This skill audits everything in vendor/ and node_modules/.


Quick start

# Composer side
cd ~/plugins/my-plugin && composer audit

# npm side
cd ~/plugins/my-plugin && npm audit

# Plus Orbit's deeper analysis
bash ~/Claude/orbit/scripts/supply-chain-audit.sh ~/plugins/my-plugin

What this skill checks

1. Known CVEs in dependencies

composer audit --format=json | jq '.advisories'
npm audit --json | jq '.vulnerabilities'

Cross-referenced with:

2. License compatibility (GPL-only for WP plugins)

Whitepaper intent: WP.org requires GPL-compatible. AGPL, BUSL, proprietary licenses break that. Auditor flags any non-compatible.

Compatible: GPL-2.0+, MIT, Apache-2.0 (permissive), BSD, LGPL. Incompatible: AGPL, BUSL, proprietary, CC-NC, "must contact author."

3. Abandoned packages

A package is "abandoned" if:
- last commit > 2 years ago
- repository archived / 404
- composer.json has "abandoned: true"
- npm registry shows "deprecated"

Abandoned = no security patches → ticking time bomb.

4. Typosquatting risk

A dependency named lodaash (with double-a) is suspicious. Auditor checks Levenshtein distance from popular packages.

5. Post-install / preinstall scripts (npm)

{
  "scripts": {
    "postinstall": "node ./postinstall.js"  ← red flag — review the script
  }
}

A malicious postinstall.js can exfiltrate secrets. Audit forces review.

6. Lockfile integrity

  • composer.lock matches composer.json?
  • package-lock.json matches package.json?
  • All hashes verified?
composer install --dry-run
npm ci  # fails if lockfile-package mismatch

7. Direct GitHub dependencies (no version pinning)

"dependencies": {
  "some-pkg": "github:user/repo"  ← no version, no integrity hash
}

→ Pin to a specific commit hash + verify hash on every install.


Output

# Supply Chain Audit — my-plugin

## Composer (15 packages)
- ✓ All GPL-compatible
- ❌ guzzlehttp/guzzle 6.5.5 — CVE-2024-XXXX (HIGH) — upgrade to 7.x
- ⚠ symfony/polyfill-iconv — abandoned (last release 18 months ago)

## npm (1,247 packages incl. transitive)
- ⚠ 14 vulnerabilities (3 HIGH, 11 LOW)
   `npm audit fix` resolves 9
- ❌ Package "lodahs" (note typo) found — looks like lodash typosquat. Investigate.
- ⚠ postinstall script in `node-pre-gyp` — common but read it
- ❌ Package `xyz-utils` — repo 404 (deleted from GitHub)

## Lockfile
- ✓ composer.lock matches composer.json
- ❌ package-lock.json out of sync with package.json — npm ci will fail

## Recommendation
1. `composer require guzzlehttp/guzzle:^7.0` — fixes critical
2. Investigate "lodahs" typo (likely safe but verify)
3. Remove `xyz-utils` (its repo is deleted)
4. `npm install` to refresh lockfile

Pair with

  • /orbit-zip-hygiene — vendor/ in release zip
  • /orbit-sec-secrets-leak — secrets in lockfiles
  • /orbit-cve-check — Orbit's own CVE feed

Sources & Evergreen References

Canonical docs

Rule lineage

  • composer audit (built-in) — Composer 2.4+ (2022)
  • Supply-chain attacks (xz-utils, event-stream) — broad awareness since 2021

Last reviewed

  • 2026-04-29 — supply-chain landscape evolves daily

When not to use it

  • When only checking for secrets in lockfiles
  • When only checking vendor/ in release zip
  • When only checking Orbit's own CVE feed

Limitations

  • License compatibility check is GPL-only for WordPress plugins
  • Abandoned package detection criteria are specific (e.g., last commit > 2 years ago)
  • Post-install/preinstall script review requires manual verification

How it compares

This skill provides a complete, multi-faceted supply chain security audit specifically for Composer and npm dependencies, integrating checks for various vulnerabilities and risks beyond what basic audit tools offer individually.

Compared to similar skills

orbit-sec-supply-chain side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
orbit-sec-supply-chain (this skill)03moReviewIntermediate
dependency-auditor19moReviewBeginner
dependency-vulnerability-triage06moReviewIntermediate
backend-security-coder244moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

dependency-auditor

alirezarezvani

Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.

16

dependency-vulnerability-triage

lichunboa

Turns npm audit/Snyk results into prioritized patch plans with severity assessment, safe upgrade paths, breaking change analysis, and rollback strategies. Use for "dependency security", "vulnerability patching", "npm audit", or "security updates".

00

backend-security-coder

sickn33

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

2446

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

3191

fix-dependabot-alerts

microsoft

Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.

1872

fix-security-vulnerability

getsentry

Analyze and propose fixes for Dependabot security alerts

716

Search skills

Search the agent skills registry