Back to catalog
Static reviewDevelopment

Skill dossier

analyzing-sbom-for-supply-chain-vulnerabilities

Source declaration

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. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

The author's original description, preserved in English. It describes intent, not verified performance.

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. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L67]
  • Step 1: Generate SBOM (if not provided) [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L69]
  • Step 2: Parse SBOM and Extract Components [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L86]
  • Step 3: Correlate Components with NVD CVE Database [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L133]
  • Step 4: Build Dependency Graph and Identify Transitive Risks [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L159]
  • Step 5: Calculate Risk Scores [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L185]
  • Step 6: Cross-Validate with Grype [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L208]
  • Step 7: Generate Compliance Report [Source statement; provisional, not tested. Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L225]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L1-L45]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
56.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/analyzing-sbom-for-supply-chain-vulnerabilities/LICENSEOther11 KB
skills/analyzing-sbom-for-supply-chain-vulnerabilities/references/api-reference.mdReference5.9 KB
skills/analyzing-sbom-for-supply-chain-vulnerabilities/scripts/agent.pyScript27.7 KB
skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.mdInstruction11.4 KB

SKILL.md frontmatter

{
  "name": "analyzing-sbom-for-supply-chain-vulnerabilities",
  "description": "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. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.\n",
  "domain": "cybersecurity",
  "subdomain": "supply-chain-security",
  "tags": [
    "SBOM",
    "CycloneDX",
    "SPDX",
    "NVD",
    "CVE",
    "supply-chain",
    "dependency-analysis",
    "syft",
    "grype"
  ],
  "version": "1.0.0",
  "author": "mukul975",
  "license": "Apache-2.0",
  "atlas_techniques": [
    "AML.T0010"
  ],
  "nist_ai_rmf": [
    "GOVERN-5.2",
    "MAP-1.6",
    "MANAGE-2.2",
    "GOVERN-1.1",
    "GOVERN-4.2"
  ],
  "nist_csf": [
    "GV.SC-01",
    "GV.SC-03",
    "GV.SC-06",
    "GV.SC-07"
  ],
  "mitre_attack": [
    "T1195.001",
    "T1195.002",
    "T1554",
    "T1190"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Decision

    Step 1: Generate SBOM (if not provided)

    Source-described decision candidate under “Step 1: Generate SBOM (if not provided)”; not verified execution.

  4. 04
    Action

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

    Source-described action candidate under “Step 1: Generate SBOM (if not provided)”; not verified execution.

  5. 05
    Action

    Step 2: Parse SBOM and Extract Components

    Source-described action candidate under “Step 2: Parse SBOM and Extract Components”; not verified execution.

  6. 06
    Action

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

    Source-described action candidate under “Step 2: Parse SBOM and Extract Components”; not verified execution.

Inspect all extracted workflow candidates (25 candidate steps)
  1. 07
    Action

    Step 3: Correlate Components with NVD CVE Database

    Source-described action candidate under “Step 3: Correlate Components with NVD CVE Database”; not verified execution.

  2. 08
    Action

    Step 4: Build Dependency Graph and Identify Transitive Risks

    Source-described action candidate under “Step 4: Build Dependency Graph and Identify Transitive Risks”; not verified execution.

  3. 09
    Action

    In-degree: How many components depend on this one (high in-degree = high blast radius)

    Source-described action candidate under “Step 4: Build Dependency Graph and Identify Transitive Risks”; not verified execution.

  4. 10
    Action

    Shortest path to root: Distance from application entry point (closer = more exploitable)

    Source-described action candidate under “Step 4: Build Dependency Graph and Identify Transitive Risks”; not verified execution.

  5. 11
    Action

    Betweenness centrality: Components that sit on many dependency paths (bottleneck risk)

    Source-described action candidate under “Step 4: Build Dependency Graph and Identify Transitive Risks”; not verified execution.

  6. 12
    Action

    Step 5: Calculate Risk Scores

    Source-described action candidate under “Step 5: Calculate Risk Scores”; not verified execution.

  7. 13
    Action

    Step 6: Cross-Validate with Grype

    Source-described action candidate under “Step 6: Cross-Validate with Grype”; not verified execution.

  8. 14
    Action

    Use grype to independently scan the SBOM and compare findings:

    Source-described action candidate under “Step 6: Cross-Validate with Grype”; not verified execution.

  9. 15
    Output

    Step 7: Generate Compliance Report

    Source-described output candidate under “Step 7: Generate Compliance Report”; not verified execution.

  10. 16
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  11. 17
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  12. 18
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  13. 19
    Action

    Collect all vendor SBOMs (CycloneDX or SPDX JSON format)

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  14. 20
    Action

    Parse each SBOM and search for log4j-core components with versions < 2.17.1

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  15. 21
    Action

    Query NVD API for the specific CVEs (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105)

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  16. 22
    Action

    Build dependency graphs to identify which application components depend on log4j

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  17. 23
    Action

    Calculate blast radius: how many services and endpoints are exposed

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  18. 24
    Output

    Generate prioritized remediation report sorted by exposure and business criticality

    Source-described output candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

  19. 25
    Action

    Cross-validate findings with grype scan of the same SBOMs

    Source-described action candidate under “Scenario: Assessing Vendor Software After Log4Shell Disclosure”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

66 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

21 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 21 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

12 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

31 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 31 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

2 occurrences

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/analyzing-sbom-for-supply-chain-vulnerabilities/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/analyzing-sbom-for-supply-chain-vulnerabilities
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.