Dependency and Supply-Chain Review
Use SLSA provenance guidance for build-evidence concepts. The broader dependency and advisory checks below are this catalog's review contract; a provenance document does not establish every supply-chain control.
Workflow
- Inventory direct and transitive dependency sources, lockfiles, registries, build tools, CI actions, and produced artifacts.
- Check version constraints, integrity hashes, immutable pins, maintainer or publisher identity, and unexpected source changes.
- Review known-vulnerability evidence using current authoritative advisory sources when network access is authorized.
- Trace the build entry point, external downloads, generated code, credentials, and artifact signing or attestation evidence.
- Use NIST SSDF outcomes to identify process gaps and SLSA provenance concepts to describe evidence.
- Assess update, rollback, revocation, dependency confusion, typosquatting, and abandoned-package exposure.
- Prioritize findings by reachability, exploitability, privilege, and ability to reproduce the build.
Boundaries
- Do not claim a SLSA level unless independently verified against every applicable requirement.
- Do not update, install, execute, or publish dependencies during a read-only review.
- Absence from an advisory feed is not proof that a dependency is safe.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Inventory, Provenance evidence, Findings, Reachability, Build risks, Recommended controls, and Claim limits. Grade each finding none, note, warning, or error, and order the list with the most severe first. No change is pinned in this review, so do not assign a finding state.
Example
Synthetic example; not an observed client result.
Input: A CI action changes from a commit SHA to a moving branch.
Output: warning: the build input is no longer immutable. Review the intended revision and restore a verified immutable reference.
1---2name: review-dependencies3description: "Reviews dependencies and build inputs when asked whether a package, lockfile update, CI action, or artifact can be trusted; checks provenance and integrity without installing it."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-dependencies7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Dependency and Supply-Chain Review1617Use [SLSA provenance guidance](https://slsa.dev/spec/v1.2/provenance) for build-evidence concepts. The broader dependency and advisory checks below are this catalog's review contract; a provenance document does not establish every supply-chain control.1819## Workflow20211. Inventory direct and transitive dependency sources, lockfiles, registries, build tools, CI actions, and produced artifacts.222. Check version constraints, integrity hashes, immutable pins, maintainer or publisher identity, and unexpected source changes.233. Review known-vulnerability evidence using current authoritative advisory sources when network access is authorized.244. Trace the build entry point, external downloads, generated code, credentials, and artifact signing or attestation evidence.255. Use NIST SSDF outcomes to identify process gaps and SLSA provenance concepts to describe evidence.266. Assess update, rollback, revocation, dependency confusion, typosquatting, and abandoned-package exposure.277. Prioritize findings by reachability, exploitability, privilege, and ability to reproduce the build.2829## Boundaries3031- Do not claim a SLSA level unless independently verified against every applicable requirement.32- Do not update, install, execute, or publish dependencies during a read-only review.33- Absence from an advisory feed is not proof that a dependency is safe.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Inventory, Provenance evidence, Findings, Reachability, Build risks, Recommended controls, and Claim limits. Grade each finding `none`, `note`, `warning`, or `error`, and order the list with the most severe first. No change is pinned in this review, so do not assign a finding state.4041## Example4243Synthetic example; not an observed client result.4445Input: A CI action changes from a commit SHA to a moving branch.4647Output: warning: the build input is no longer immutable. Review the intended revision and restore a verified immutable reference.