supply-chain-security-reviewer

Review software supply-chain exposure across dependencies, build steps, and CI/CD workflows.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill supply-chain-security-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-security-reviewer
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/supply-chain-security-reviewer
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill supply-chain-security-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you assess whether software can be compromised through its dependencies, build process, or CI/CD pipeline, rather than only through first-party code vulnerabilities.

Core Features & Use Cases

  • Dependency Risk Review: Triage lockfiles and scanner output by reachability, so reachable issues are separated from latent or irrelevant findings.
  • Build and CI Security Review: Inspect install scripts, postinstall hooks, GitHub Actions, and other pipeline steps for untrusted triggers, secret exposure, and unpinned third-party actions.
  • Provenance and Pinning Checks: Evaluate whether packages, artifacts, models, datasets, and agentic components are pinned, sourced safely, and accompanied by trustworthy integrity signals.
  • Use Case: A team preparing to publish a repository can use this Skill to identify the dependency, workflow, or artifact paths that could lead to code execution or secret theft.

Quick Start

Ask the supply-chain security reviewer to inspect the repository’s lockfiles, install scripts, and CI workflows for reachable compromise paths and concrete remediation steps.

Frequently Asked Questions about supply-chain-security-reviewer

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

FAQPage Schema
How do I review software supply chain security risks in my dependencies and CI workflows?

Supply chain security review involves triaging lockfiles, install scripts, and CI workflows for reachable compromise paths. You assess dependencies by reachability to separate exploitable issues from latent findings, then apply remediation like pinning, upgrading, or isolating risky paths.

What is dependency reachability analysis for lockfile triage?

Dependency reachability analysis evaluates lockfile scanner output to determine if a vulnerable dependency is actually callable in your code. It separates reachable supply chain risks that require immediate remediation from latent or irrelevant findings that pose lower threat.

How do I check GitHub Actions workflows for unpinned actions and secret exposure?

CI security review inspects workflow triggers, permissions, and third-party actions for untrusted inputs and secret exposure. You identify unpinned actions in your GitHub workflows and apply concrete remediation by pinning them to specific versions or removing risky pipeline steps.

Can I use this to review provenance and pinning for packages, models, and datasets?

Yes, provenance checks evaluate whether packages, artifacts, models, datasets, and agentic components are pinned and sourced safely. The review verifies trustworthy integrity signals are present and recommends pinning, upgrading, or removing components lacking proper provenance verification.

How do I assess install-time execution risks from postinstall hooks?

Build security review inspects install scripts and postinstall hooks for untrusted code execution paths. You analyze install-time execution in your dependencies to identify scripts that could lead to compromise, then apply remediation by removing or isolating those risky paths.

What's the best way to triage dependency scanner output by exploitability?

Exploitability-based triage requires evaluating scanner findings against reachability and workflow exposure to produce concrete verdicts. You separate reachable supply chain risks requiring action from noise, then output remediation steps like pinning, upgrading, removing, or isolating the affected dependencies.