agentleFS
Sign inStart free
HayatelinHayatelin/devsecops-skills/skills/sbom-generation/SKILL.md

sbom-generation

Skill0 starsChanged 5 months agoMITView on GitHub

Generate a Software Bill of Materials (SBOM) and use it to track and remediate vulnerable components. Use when the user needs an SBOM for compliance (e.g. SSDF, EU CRA), wants full visibility into dependencies and licenses, or is setting up continuous supply-chain monitoring.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. kaandgnsh/Claude-Blue★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

Create a free account to mount
Files
SKILL.md

sbom-generation — know exactly what you ship

When to use

The user needs an SBOM for compliance/customers, wants a complete inventory of direct + transitive dependencies and their licenses, or wants to continuously watch shipped artifacts for newly-disclosed CVEs.

Process

  1. Pick a format: CycloneDX (security-focused, common) or SPDX (license/compliance).
  2. Generate from the source/artifact:
    • General / containers: syft <dir-or-image> -o cyclonedx-json > sbom.json
    • Node: cdxgen -o sbom.json · Python: cyclonedx-py environment
    • Or build-tool plugins (Maven/Gradle/Cargo) for the most accurate graph.
  3. Scan the SBOM for vulnerabilities: grype sbom:sbom.json or osv-scanner --sbom sbom.json.
  4. Triage by severity + reachability + fix availability; record accepted risks.
  5. Automate: regenerate the SBOM in CI on every release, store it as a build artifact, and re-scan stored SBOMs on a schedule so you catch CVEs disclosed after you shipped.

What to check

  • Direct AND transitive components are present (a shallow SBOM is misleading).
  • Each component has a version and, ideally, a license.
  • The SBOM is generated from the real build, not a guessed manifest.

How to fix / act

  • For each vulnerable component: upgrade to the patched version, or document a justified exception (with reachability rationale and an expiry date).
  • Flag GPL/AGPL or unknown licenses to the user if the project ships commercially.

Report back

Give the component count, top vulnerable components (by severity + fix availability), any risky licenses, and where the SBOM is stored.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free