analyzing-sbom-for-supply-chain-vulnerabilities

analyzing-sbom-for-supply-chain-vulnerabilities is a skill for Claude Code from 26zl/cybersec-toolkit. It costs 110 tokens per session (3,122 once invoked), scanned A, a copy of analyzing-sbom-for-supply-chain-vulnerabilities, MIT.

A software-supply-chain security workflow for analyzing an SBOM, a file listing the libraries and components inside software. It checks CycloneDX and SPDX files against the NVD database of published software vulnerabilities.

In plain words
What is it for?
Use it to review vendor SBOMs, find vulnerable direct or indirect dependencies, check whether a new CVE affects deployed software, and produce supply-chain risk reports.
Why use it?
Third-party and indirect dependencies can contain known vulnerabilities that are easy to miss. This workflow shows affected components, dependency paths, risk scores, and compliance information.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the cybersec-toolkit plugin — 197 skills, 2 hooks, 1 MCP server shipped together

Good fit Use it to review vendor SBOMs, find vulnerable direct or indirect dependencies, check whether a new CVE affects deployed software, and produce supply-chain risk reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add 26zl/cybersec-toolkit --skill analyzing-sbom-for-supply-chain-vulnerabilities
Clone the repo
git clone --depth 1 https://github.com/26zl/cybersec-toolkit

Made for: Claude Code.

Or install cybersec-toolkit, the plugin that ships this one along with the rest of its 197 skills, 2 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-sbom-for-supply-chain-vulnerabilities

README.md
[![agentmods](https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities/github.svg)](https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities)
Your own site
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyzing-sbom-for-supply-chain-vulnerabilities

Your own site · 80×15
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-sbom-for-supply-chain-vulnerabilities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.03122
Opus 5 $0.00055 $0.01561
Sonnet 5 $0.00022 $0.00624
Haiku 4.5 $0.00011 $0.00312

Measured 8d ago against content hash 23d96721e66f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyzing-sbom-for-supply-chain-vulnerabilities scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/agent.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

resp = requests.get(NVD_API, params=params, headers=headers, timeout=30)
Origin

This is a copy

100% identical to analyzing-sbom-for-supply-chain-vulnerabilities — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md · 311 lines

How it starts

The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing SBOM for Supply Chain Vulnerabilities

When to Use

  • A new regulatory requirement (EO 14028, EU CRA) mandates SBOM analysis for software deliveries
  • Security team needs to assess third-party risk by scanning vendor-provided SBOMs
  • CI/CD pipeline requires automated vulnerability checks against generated SBOMs
  • Incident response needs to determine if a newly disclosed CVE affects deployed software
  • Procurement team requires supply chain risk assessment for a software acquisition

Do not use for runtime vulnerability scanning of live systems; use container scanning tools (Trivy, Grype CLI) or host-based vulnerability scanners (Nessus, Qualys) instead.

Prerequisites

Workflow

Step 1: Generate SBOM (if not provided)

Use syft to create an SBOM from a container image or project directory:

# Generate CycloneDX JSON from a container image
syft alpine:latest -o cyclonedx-json > sbom-cyclonedx.json

# Generate SPDX JSON from a project directory
syft dir:/path/to/project -o spdx-json > sbom-spdx.json

# Generate from a running container
syft docker:my-app-container -o cyclonedx-json > sbom.json

Syft supports over 30 package ecosystems including npm, PyPI, Maven, Go modules, apt, apk, and RPM. The generated SBOM includes package names, versions, licenses, CPE identifiers, and PURL (Package URL) references.

Step 2: Parse SBOM and Extract Components

Parse the SBOM to extract all software components with their identifiers:

CycloneDX JSON Structure:

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.5",
  "components": [
    {
      "type": "library",
      "name": "lodash",
      "version": "4.17.20",
      "purl": "pkg:npm/[email protected]",
      "cpe": "cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:*:*:*",
      "licenses": [{"license": {"id": "MIT"}}]
    }
  ],
  "dependencies": [
    {"ref": "pkg:npm/[email protected]", "dependsOn": ["pkg:npm/[email protected]"]}
  ]
}

Read the full file on GitHub · 311 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 311 lines · 110 tokens per session scan A 23d96721e66f

Subscribe to this mod's changes

analyzing-sbom-for-supply-chain-vulnerabilities is a skill published in the GitHub repository 26zl/cybersec-toolkit (54 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 3,122 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to analyzing-sbom-for-supply-chain-vulnerabilities, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

analyzing-sbom-for-supply-chain-vulnerabilities

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…

adriannoes/awesome-agentic-ai · 110 tokens

analyzing-sbom-for-supply-chain-vulnerabilities

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…

pinkpixel-dev/skills-collection-1 · 110 tokens

analyzing-sbom-for-supply-chain-vulnerabilities

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…

Youngmaidainon/Agent-Level-Up · 110 tokens

analyzing-sbom-for-supply-chain-vulnerabilities

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…

marysatasselshaped667/skills-collection-1 · 110 tokens

generating-and-analyzing-sboms

Produce and ingest CycloneDX and SPDX SBOMs and correlate them to vulnerability intelligence.

adriannoes/awesome-agentic-ai · 28 tokens

sbom-syft

Software Bill of Materials (SBOM) generation using Syft for container images, filesystems, and archives. Detects packages across 28+ ecosystems with multi-format output support (CycloneDX, SPDX, syft-json). Enables vulnerability assessment, license compliance, and supply chain security. Use when: (1) Generating SBOMs…

AgentSecOps/SecOpsAgentKit · 133 tokens