supply-chain-review

Guides Rust dependency supply-chain risk triage during PR and release reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill supply-chain-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-review
Source: https://github.com/Pandaala/Edgion/tree/main/skills/04-review/supply-chain
Command: npx skills add https://github.com/Pandaala/Edgion --skill supply-chain-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Supply-chain reviews prevent insecure or incompatible Rust dependencies from entering Edgion by standardizing how to audit lockfile changes, new crates, MSRV impacts, and license risk.

Core Features & Use Cases

  • Actionable threat-model triage: Evaluates malicious upstream risk, transitive vulnerabilities, abandoned/maintenance-mode risk, MSRV drift, and license/maintenance-mode crate concerns.
  • Repeatable tooling workflow: Defines when to run cargo audit and cargo deny, plus when to do manual lockfile diffs.
  • Clear decision rules: Establishes severity-based merge/deferral behavior (block on high/critical, document medium/low outcomes, re-evaluate on triggers) and specifies acceptance criteria for maintenance-mode crates via a dedicated rule file.

Quick Start

Use the supply-chain-review skill when reviewing a PR that modifies Cargo.lock, adds new crates, updates MSRV-related metadata, or introduces a dependency licensing concern so you can document the decision using the triage rules in this directory.

Frequently Asked Questions about supply-chain-review

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

FAQPage Schema
How do I triage Rust dependency risks when reviewing a PR that modifies Cargo.lock?

To triage Rust dependency risks during PR review, audit lockfile changes by running cargo audit for RUSTSEC advisories and cargo deny for license compliance, then document severity-based merge decisions for malicious upstream or transitive vulnerabilities.

What is the best way to enforce license compliance for Rust crates before release?

The best way to enforce license compliance before release is to run cargo deny to check for copyleft or non-commercial licenses, document acceptance decisions for maintenance-mode crates, and block merges if high-severity license violations are found.

How do I handle MSRV drift when updating Rust dependencies?

To handle MSRV drift when updating Rust dependencies, evaluate MSRV-related metadata changes in the PR, determine if the new Minimum Supported Rust Version impacts project compatibility, and document the acceptance decision using established triage rules.

Can I use cargo audit to detect abandoned or maintenance-mode Rust crates?

Yes, cargo audit identifies RUSTSEC advisories that often flag abandoned or maintenance-mode Rust crates, allowing you to apply severity-based actions and document re-evaluation triggers in-repo for acceptance.

When should I manually diff Cargo.lock instead of just running automated tools?

You should manually diff Cargo.lock when reviewing PRs that add new crates or update dependencies, as manual inspection complements cargo audit and cargo deny by catching malicious upstream risk and transitive vulnerabilities not yet listed in advisories.