Dependency and SBOM audit

Triage known risks in supplied lockfiles, bills of materials, and scanner reports.

Customize the recipe

0/1500 characters

Prompt preview

# Dependency and SBOM audit

Triage known risks in supplied lockfiles, bills of materials, and scanner reports.

## Read-only scope
Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient.

Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files.

## Tools and setup · Universal
Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions.

- [Security Best Practices](https://github.com/openai/skills/blob/main/skills/.curated/security-best-practices/SKILL.md) (Skill) — Use the language-specific guidance to identify insecure defaults and review supplied code.
- [OSV-Scanner](https://github.com/google/osv-scanner) (Repository) — Interpret dependency advisories in supplied scan results and match them to locked package versions.
- [Trivy](https://github.com/aquasecurity/trivy) (Repository) — Review existing dependency, image, and configuration findings against local manifests and inventory.
- [OpenSSF Scorecard](https://github.com/ossf/scorecard) (Repository) — Review software supply-chain practices using available scorecard reports and repository configuration.

## Workflow
Reconcile the supplied lockfiles and SBOM with existing advisory results. Deduplicate findings by package and advisory, distinguish direct and transitive dependencies, and prioritize versions relevant to the deployed inventory.

## Deliverable
A dependency risk inventory with package versions, advisory references, recommended upgrades, and uncertainty.
- Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient.

## Acceptance checks
- [ ] Each advisory finding maps to an affected package version in the supplied inventory.
- [ ] Mark stale scan dates, uncertain reachability, and incomplete dependency mappings.
- [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps.
- [ ] Redact credentials, tokens, personal data, and sensitive values in the report.

Recipe resources

Source, setup, and compatibility details.