perseus-supply-chain

Identify dependencies and surface supply chain risks across supported language manifests.

66|14|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kaivyy/perseus --skill perseus-supply-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perseus-supply-chain
Source: https://github.com/kaivyy/perseus/tree/main/skills/perseus/specialists/supply-chain
Command: npx skills add https://github.com/kaivyy/perseus --skill perseus-supply-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supply chain risks in software dependencies, including CVEs, typosquatting, and license conflicts, are identified and prioritized to prevent compromised code.

Core Features & Use Cases

  • Manifest discovery across supported languages (package.json, go.mod, pyproject.toml, etc.)
  • CVE analysis for dependencies with cross-language coverage
  • Typosquatting detection and dependency confusion risk assessment
  • License compliance review and risk mitigation
  • Lockfile integrity and reproducible builds validation
  • Deliverable generation with remediation guidance for engineers and executives

Quick Start

Run /scan to trigger manifest discovery and begin the supply chain risk assessment across your project.

Frequently Asked Questions about perseus-supply-chain

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

FAQPage Schema
How do I scan dependencies for supply chain risks in my codebase?

To scan dependencies for supply chain risks, trigger manifest discovery to enumerate dependencies across JavaScript, Go, Python, Rust, Java, Ruby, and C# projects. The analysis applies CVE checks, typosquatting detection, license review, and lockfile integrity validation to produce a structured deliverable with remediation guidance.

What manifests are supported for dependency confusion and CVE analysis?

Supported manifests for dependency confusion and CVE analysis include package.json, go.mod, pyproject.toml, and pom.xml. The tool discovers these files across JavaScript, Go, Python, Rust, Java, Ruby, and C# projects to enumerate dependencies and surface supply chain risks.

Does supply chain risk analysis check for typosquatting and license compliance issues?

Supply chain risk analysis does check for typosquatting and license compliance issues. It identifies and prioritizes these risks alongside CVEs and dependency confusion to prevent compromised code, generating a deliverable with mitigation guidance for both engineers and executives.

How does lockfile integrity validation work during dependency risk assessment?

Lockfile integrity validation works during dependency risk assessment by checking lockfiles to ensure reproducible builds and verify that resolved dependencies match expected states. This process surfaces discrepancies that could indicate supply chain compromise or unauthorized package modifications.

Can I use this supply chain tool with Python and Rust projects?

You can use this supply chain tool with Python and Rust projects. It discovers manifests like pyproject.toml for Python and applies cross-language CVE checks, typosquatting detection, and license review to enumerate dependencies and surface risks across both ecosystems.