orbit-sec-supply-chain

Audit Composer and npm dependencies for CVEs, licenses, and typosquatting risks.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-sec-supply-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-sec-supply-chain
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-sec-supply-chain
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-sec-supply-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in ensuring supply chain security by auditing Composer and npm dependencies, checking for license compatibility, detecting abandoned packages, and identifying potential risks such as typosquatting, post-install scripts, lockfile integrity, and direct GitHub dependencies without version pinning.

Core Features & Use Cases

  • Dependency Security: Checks for known CVEs in dependencies, providing insights on potential security risks.
  • License Compliance: Verifies that dependencies are GPL-compatible, ensuring compliance with WordPress.org requirements.
  • Abandoned Package Detection: Identifies abandoned packages that could pose security risks due to lack of updates.
  • Typosquatting Risk Assessment: Flags suspicious package names that might be typosquatting popular ones.
  • Lockfile Integrity: Ensures the integrity of lockfiles against composer.json or package.json, preventing mismatched installations.
  • Direct GitHub Dependency Handling: Pinning to specific commit hashes for security and version control.
  • Use Case: For a WordPress plugin development team looking to secure their plugin's dependencies against potential security vulnerabilities before release.

Quick Start

Run the skill with the following commands within your plugin directory: composer audit and npm audit. For deeper analysis, use Orbit's script: bash ~/Claude/orbit/scripts/supply-chain-audit.sh ~/plugins/my-plugin.

Frequently Asked Questions about orbit-sec-supply-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check npm and Composer dependencies for known CVEs?

To check npm and Composer dependencies for CVEs, run an audit script against your project directory that scans lockfiles for known vulnerabilities. It flags security risks in your PHP and JavaScript packages to resolve before release.

What is dependency typosquatting risk and how do I detect it?

Dependency typosquatting risk occurs when malicious packages mimic popular names to trick developers into installation. The audit detects this by flagging suspicious package names in your npm and Composer dependency lists.

How do I verify license compliance for WordPress plugin dependencies?

Verify WordPress plugin license compliance by auditing dependencies to ensure they are GPL-compatible. The audit checks your Composer and npm packages against compliance requirements required for WordPress.org submissions.

Can I detect abandoned packages in my npm and Composer supply chain?

Yes, you can detect abandoned packages in your npm and Composer supply chain by running an audit that identifies packages lacking recent updates. This flags dependencies that may pose security risks due to lack of maintenance.

How do I ensure lockfile integrity against composer.json and package.json?

Ensure lockfile integrity by running an audit that compares your lockfile against composer.json or package.json. This prevents mismatched installations and verifies that your locked dependency versions match your manifest configurations.

Does the supply chain audit work for both PHP and JavaScript projects?

Yes, the supply chain audit works for both PHP and JavaScript projects by scanning both Composer and npm dependencies. It provides a thorough dependency security assessment covering CVEs, licenses, and lockfile integrity for mixed-language projects.