[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B4XQJC4S29Z5R20FD03051":3,"skill-same:01M7B4XQJC4S29Z5R20FD03051":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":13,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M7B4XQJC4S29Z5R20FD03051","analyzing-sbom-for-supply-chain-vulnerabilities",null,"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\u002FSPDX parsing, or CVE correlation.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-sbom-for-supply-chain-vulnerabilities\ndescription: 'Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON\n  formats to identify supply chain vulnerabilities by correlating components against\n  the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk\n  scores, identifies transitive vulnerability paths, and generates compliance reports.\n  Activates for requests involving SBOM analysis, software composition analysis, supply\n  chain security assessment, dependency vulnerability scanning, CycloneDX\u002FSPDX parsing,\n  or CVE correlation.\n\n  '\ndomain: cybersecurity\nsubdomain: supply-chain-security\ntags:\n- SBOM\n- CycloneDX\n- SPDX\n- NVD\n- CVE\n- supply-chain\n- dependency-analysis\n- syft\n- grype\nversion: 1.0.0\nauthor: mukul975\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0010\nnist_ai_rmf:\n- GOVERN-5.2\n- MAP-1.6\n- MANAGE-2.2\n- GOVERN-1.1\n- GOVERN-4.2\nnist_csf:\n- GV.SC-01\n- GV.SC-03\n- GV.SC-06\n- GV.SC-07\nmitre_attack:\n- T1195.001\n- T1195.002\n- T1554\n- T1190\n---\n\n# Analyzing SBOM for Supply Chain Vulnerabilities\n\n## When to Use\n\n- A new regulatory requirement (EO 14028, EU CRA) mandates SBOM analysis for software deliveries\n- Security team needs to assess third-party risk by scanning vendor-provided SBOMs\n- CI\u002FCD pipeline requires automated vulnerability checks against generated SBOMs\n- Incident response needs to determine if a newly disclosed CVE affects deployed software\n- Procurement team requires supply chain risk assessment for a software acquisition\n\n**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.\n\n## Prerequisites\n\n- SBOM file in CycloneDX JSON (v1.4+) or SPDX JSON (v2.3+) format\n- Python 3.9+ with requests, networkx, and packaging libraries installed\n- NVD API key (free, from https:\u002F\u002Fnvd.nist.gov\u002Fdevelopers\u002Frequest-an-api-key) for higher rate limits\n- Network access to NVD API (https:\u002F\u002Fservices.nvd.nist.gov\u002Frest\u002Fjson\u002Fcves\u002F2.0)\n- Optionally: syft for SBOM generation, grype for cross-validation\n\n## Workflow\n\n### Step 1: Generate SBOM (if not provided)\n\nUse syft to create an SBOM from a container image or project directory:\n\n```bash\n# Generate CycloneDX JSON from a container image\nsyft alpine:latest -o cyclonedx-json > sbom-cyclonedx.json\n\n# Generate SPDX JSON from a project directory\nsyft dir:\u002Fpath\u002Fto\u002Fproject -o spdx-json > sbom-spdx.json\n\n# Generate from a running container\nsyft docker:my-app-container -o cyclonedx-json > sbom.json\n```\n\nSyft 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.\n\n### Step 2: Parse SBOM and Extract Components\n\nParse the SBOM to extract all software components with their identifiers:\n\n**CycloneDX JSON Structure:**\n```json\n{\n  \"bomFormat\": \"CycloneDX\",\n  \"specVersion\": \"1.5\",\n  \"components\": [\n    {\n      \"type\": \"library\",\n      \"name\": \"lodash\",\n      \"version\": \"4.17.20\",\n      \"purl\": \"pkg:npm\u002Flodash@4.17.20\",\n      \"cpe\": \"cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:*:*:*\",\n      \"licenses\": [{\"license\": {\"id\": \"MIT\"}}]\n    }\n  ],\n  \"dependencies\": [\n    {\"ref\": \"pkg:npm\u002Fexpress@4.18.2\", \"dependsOn\": [\"pkg:npm\u002Flodash@4.17.20\"]}\n  ]\n}\n```\n\n**SPDX JSON Structure:**\n```json\n{\n  \"spdxVersion\": \"SPDX-2.3\",\n  \"packages\": [\n    {\n      \"name\": \"lodash\",\n      \"versionInfo\": \"4.17.20\",\n      \"externalRefs\": [\n        {\"referenceType\": \"purl\", \"referenceLocator\": \"pkg:npm\u002Flodash@4.17.20\"},\n        {\"referenceType\": \"cpe23Type\", \"referenceLocator\": \"cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:*:*:*\"}\n      ],\n      \"licenseConcluded\": \"MIT\"\n    }\n  ],\n  \"relationships\": [\n    {\"spdxElementId\": \"SPDXRef-express\", \"relatedSpdxElement\": \"SPDXRef-lodash\",\n     \"relationshipType\": \"DEPENDS_ON\"}\n  ]\n}\n```\n\n### Step 3: Correlate Components with NVD CVE Database\n\nQuery the NVD 2.0 API to find known vulnerabilities for each component:\n\n```python\nimport requests\n\nNVD_API = \"https:\u002F\u002Fservices.nvd.nist.gov\u002Frest\u002Fjson\u002Fcves\u002F2.0\"\n\ndef search_cves_by_cpe(cpe_name, api_key=None):\n    params = {\"cpeName\": cpe_name, \"resultsPerPage\": 50}\n    headers = {\"apiKey\": api_key} if api_key else {}\n    resp = requests.get(NVD_API, params=params, headers=headers, timeout=30)\n    resp.raise_for_status()\n    return resp.json().get(\"vulnerabilities\", [])\n\ndef search_cves_by_keyword(keyword, version=None, api_key=None):\n    params = {\"keywordSearch\": keyword, \"resultsPerPage\": 50}\n    headers = {\"apiKey\": api_key} if api_key else {}\n    resp = requests.get(NVD_API, params=params, headers=headers, timeout=30)\n    resp.raise_for_status()\n    return resp.json().get(\"vulnerabilities\", [])\n```\n\nThe NVD API supports searching by CPE name (most precise), keyword, CVE ID, and date ranges. Rate limits: 5 requests\u002F30 seconds without API key, 50 requests\u002F30 seconds with key.\n\n### Step 4: Build Dependency Graph and Identify Transitive Risks\n\nConstruct a directed graph of dependencies to trace vulnerability propagation:\n\n```python\nimport networkx as nx\n\ndef build_dependency_graph(sbom):\n    G = nx.DiGraph()\n    # Add nodes for each component\n    for comp in sbom[\"components\"]:\n        G.add_node(comp[\"purl\"], name=comp[\"name\"], version=comp[\"version\"])\n    # Add edges from dependency relationships\n    for dep in sbom.get(\"dependencies\", []):\n        for child in dep.get(\"dependsOn\", []):\n            G.add_edge(dep[\"ref\"], child)\n    return G\n```\n\nTransitive dependency analysis identifies components that are not directly included but are pulled in through dependency chains. A vulnerability in a deeply nested transitive dependency (e.g., 4 levels deep) still represents risk but may be harder to remediate.\n\nKey graph metrics for risk assessment:\n- **In-degree**: How many components depend on this one (high in-degree = high blast radius)\n- **Shortest path to root**: Distance from application entry point (closer = more exploitable)\n- **Betweenness centrality**: Components that sit on many dependency paths (bottleneck risk)\n\n### Step 5: Calculate Risk Scores\n\nAggregate vulnerability data into component and overall risk scores:\n\n```\nRisk Score Calculation:\n━━━━━━━━━━━━━━━━━━━━━━\nComponent Risk = max(CVSS scores of all CVEs affecting the component)\n\nWeighted Risk = Component Risk * Dependency Factor\n  where Dependency Factor = 1.0 + (0.1 * in_degree)\n  (more dependents = higher organizational impact)\n\nOverall SBOM Risk = weighted average of all component risks\n  weighted by dependency centrality\n\nRisk Levels:\n  CRITICAL: CVSS >= 9.0 or known exploited (CISA KEV)\n  HIGH:     CVSS >= 7.0\n  MEDIUM:   CVSS >= 4.0\n  LOW:      CVSS \u003C 4.0\n```\n\n### Step 6: Cross-Validate with Grype\n\nUse grype to independently scan the SBOM and compare findings:\n\n```bash\n# Scan CycloneDX SBOM with grype\ngrype sbom:sbom-cyclonedx.json -o json > grype-results.json\n\n# Scan SPDX SBOM\ngrype sbom:sbom-spdx.json -o table\n\n# Filter by severity\ngrype sbom:sbom-cyclonedx.json --only-fixed --fail-on critical\n```\n\nGrype pulls vulnerability data from NVD, GitHub Security Advisories, Alpine SecDB, Red Hat, Debian, Ubuntu, Amazon Linux, and Oracle security databases, providing broader coverage than NVD alone.\n\n### Step 7: Generate Compliance Report\n\nProduce a structured report suitable for regulatory compliance:\n\n```\nSBOM VULNERABILITY ANALYSIS REPORT\n====================================\nSBOM File:         app-sbom-cyclonedx.json\nFormat:            CycloneDX v1.5\nAnalysis Date:     2026-03-19\nTotal Components:  247\nTotal Dependencies: 1,842 (direct: 34, transitive: 213)\n\nVULNERABILITY SUMMARY\n  Critical:  3 components \u002F 5 CVEs\n  High:      11 components \u002F 18 CVEs\n  Medium:    27 components \u002F 41 CVEs\n  Low:       8 components \u002F 12 CVEs\n\nCRITICAL FINDINGS\n1. lodash@4.17.20\n   CVE-2021-23337 (CVSS 7.2) - Command Injection via template\n   CVE-2020-28500 (CVSS 5.3) - ReDoS in trimEnd\n   Dependents: 14 components (high blast radius)\n   Fix: Upgrade to 4.17.21+\n\n2. log4j-core@2.14.1\n   CVE-2021-44228 (CVSS 10.0) - Log4Shell RCE [CISA KEV]\n   CVE-2021-45046 (CVSS 9.0) - Incomplete fix bypass\n   Dependents: 8 components\n   Fix: Upgrade to 2.17.1+\n\nDEPENDENCY GRAPH RISKS\n  Most depended-on: core-util@1.2.3 (47 dependents)\n  Deepest chain: app -> framework -> adapter -> codec -> zlib (5 levels)\n  Bottleneck components: 3 components on >50% of dependency paths\n\nLICENSE COMPLIANCE\n  Copyleft licenses found: 2 (GPL-3.0 in libxml2, AGPL-3.0 in mongodb-driver)\n  Review required for commercial distribution\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **SBOM** | Software Bill of Materials; a formal inventory of all components, libraries, and dependencies in a software product |\n| **CycloneDX** | OWASP-maintained SBOM standard supporting JSON, XML, and protobuf formats with dependency graph and vulnerability data |\n| **SPDX** | Linux Foundation SBOM standard focused on license compliance with support for package, file, and snippet-level detail |\n| **PURL** | Package URL; a standardized scheme for identifying software packages across ecosystems (e.g., pkg:npm\u002Flodash@4.17.21) |\n| **CPE** | Common Platform Enumeration; NIST naming scheme for IT products used to correlate with NVD CVE data |\n| **NVD** | National Vulnerability Database; US government repository of vulnerability data indexed by CVE identifiers |\n| **Transitive Dependency** | A dependency not directly declared but pulled in through the dependency chain of direct dependencies |\n| **CISA KEV** | CISA Known Exploited Vulnerabilities catalog; CVEs confirmed to be actively exploited in the wild |\n\n## Tools & Systems\n\n- **syft** (Anchore): Open-source SBOM generator supporting 30+ package ecosystems and CycloneDX\u002FSPDX output\n- **grype** (Anchore): Vulnerability scanner that accepts SBOMs as input and correlates against multiple advisory databases\n- **cyclonedx-python-lib**: Python library for creating, parsing, and validating CycloneDX SBOMs programmatically\n- **lib4sbom**: Python library for parsing both SPDX and CycloneDX format SBOMs\n- **nvdlib**: Python wrapper for the NVD 2.0 API supporting CVE and CPE queries with rate limit management\n- **OWASP Dependency-Track**: Platform for continuous SBOM analysis, vulnerability tracking, and policy enforcement\n\n## Common Scenarios\n\n### Scenario: Assessing Vendor Software After Log4Shell Disclosure\n\n**Context**: After the Log4Shell (CVE-2021-44228) disclosure, the security team needs to determine which vendor-supplied applications contain vulnerable versions of log4j. Several vendors have provided SBOMs per contractual requirements.\n\n**Approach**:\n1. Collect all vendor SBOMs (CycloneDX or SPDX JSON format)\n2. Parse each SBOM and search for log4j-core components with versions \u003C 2.17.1\n3. Query NVD API for the specific CVEs (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105)\n4. Build dependency graphs to identify which application components depend on log4j\n5. Calculate blast radius: how many services and endpoints are exposed\n6. Generate prioritized remediation report sorted by exposure and business criticality\n7. Cross-validate findings with grype scan of the same SBOMs\n\n**Pitfalls**:\n- Vendor SBOMs may be incomplete, missing shaded\u002Fbundled JAR files that embed log4j\n- SPDX and CycloneDX version differences may affect parser compatibility\n- NVD API rate limits can slow analysis when scanning hundreds of components without an API key\n- CPE names in SBOMs may not exactly match NVD entries, requiring fuzzy matching\n- Transitive dependencies may include log4j even when it is not a direct dependency\n","# Analyzing SBOM for Supply Chain Vulnerabilities\n\n## When to Use\n\n- A new regulatory requirement (EO 14028, EU CRA) mandates SBOM analysis for software deliveries\n- Security team needs to assess third-party risk by scanning vendor-provided SBOMs\n- CI\u002FCD pipeline requires automated vulnerability checks against generated SBOMs\n- Incident response needs to determine if a newly disclosed CVE affects deployed software\n- Procurement team requires supply chain risk assessment for a software acquisition\n\n**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.\n\n## Prerequisites\n\n- SBOM file in CycloneDX JSON (v1.4+) or SPDX JSON (v2.3+) format\n- Python 3.9+ with requests, networkx, and packaging libraries installed\n- NVD API key (free, from https:\u002F\u002Fnvd.nist.gov\u002Fdevelopers\u002Frequest-an-api-key) for higher rate limits\n- Network access to NVD API (https:\u002F\u002Fservices.nvd.nist.gov\u002Frest\u002Fjson\u002Fcves\u002F2.0)\n- Optionally: syft for SBOM generation, grype for cross-validation\n\n## Workflow\n\n### Step 1: Generate SBOM (if not provided)\n\nUse syft to create an SBOM from a container image or project directory:\n\n```bash\n# Generate CycloneDX JSON from a container image\nsyft alpine:latest -o cyclonedx-json > sbom-cyclonedx.json\n\n# Generate SPDX JSON from a project directory\nsyft dir:\u002Fpath\u002Fto\u002Fproject -o spdx-json > sbom-spdx.json\n\n# Generate from a running container\nsyft docker:my-app-container -o cyclonedx-json > sbom.json\n```\n\nSyft 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.\n\n### Step 2: Parse SBOM and Extract Components\n\nParse the SBOM to extract all software components with their identifiers:\n\n**CycloneDX JSON Structure:**\n```json\n{\n  \"bomFormat\": \"CycloneDX\",\n  \"specVersion\": \"1.5\",\n  \"components\": [\n    {\n      \"type\": \"library\",\n      \"name\": \"lodash\",\n      \"version\": \"4.17.20\",\n      \"purl\": \"pkg:npm\u002Flodash@4.17.20\",\n      \"cpe\": \"cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:*:*:*\",\n      \"licenses\": [{\"license\": {\"id\": \"MIT\"}}]\n    }\n  ],\n  \"dependencies\": [\n    {\"ref\": \"pkg:npm\u002Fexpress@4.18.2\", \"dependsOn\": [\"pkg:npm\u002Flodash@4.17.20\"]}\n  ]\n}\n```\n\n**SPDX JSON Structure:**\n```json\n{\n  \"spdxVersion\": \"SPDX-2.3\",\n  \"packages\": [\n    {\n      \"name\": \"lodash\",\n      \"versionInfo\": \"4.17.20\",\n      \"externalRefs\": [\n        {\"referenceType\": \"purl\", \"referenceLocator\": \"pkg:npm\u002Flodash@4.17.20\"},\n        {\"referenceType\": \"cpe23Type\", \"referenceLocator\": \"cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:*:*:*\"}\n      ],\n      \"licenseConcluded\": \"MIT\"\n    }\n  ],\n  \"relationships\": [\n    {\"spdxElementId\": \"SPDXRef-express\", \"relatedSpdxElement\": \"SPDXRef-lodash\",\n     \"relationshipType\": \"DEPENDS_ON\"}\n  ]\n}\n```\n\n### Step 3: Correlate Components with NVD CVE Database\n\nQuery the NVD 2.0 API to find known vulnerabilities for each component:\n\n```python\nimport requests\n\nNVD_API = \"https:\u002F\u002Fservices.nvd.nist.gov\u002Frest\u002Fjson\u002Fcves\u002F2.0\"\n\ndef search_cves_by_cpe(cpe_name, api_key=None):\n    params = {\"cpeName\": cpe_name, \"resultsPerPage\": 50}\n    headers = {\"apiKey\": api_key} if api_key else {}\n    resp = requests.get(NVD_API, params=params, headers=headers, timeout=30)\n    resp.raise_for_status()\n    return resp.json().get(\"vulnerabilities\", [])\n\ndef search_cves_by_keyword(keyword, version=None, api_key=None):\n    params = {\"keywordSearch\": keyword, \"resultsPerPage\": 50}\n    headers = {\"apiKey\": api_key} if api_key else {}\n    resp = requests.get(NVD_API, params=params, headers=headers, timeout=30)\n    resp.raise_for_status()\n    return resp.json().get(\"vulnerabilities\", [])\n```\n\nThe NVD API supports searching by CPE name (most precise), keyword, CVE ID, and date ranges. Rate limits: 5 requests\u002F30 seconds without API key, 50 requests\u002F30 seconds with key.\n\n### Step 4: Build Dependency Graph and Identify Transitive Risks\n\nConstruct a directed graph of dependencies to trace vulnerability propagation:\n\n```python\nimport networkx as nx\n\ndef build_dependency_graph(sbom):\n    G = nx.DiGraph()\n    # Add nodes for each component\n    for comp in sbom[\"components\"]:\n        G.add_node(comp[\"purl\"], name=comp[\"name\"], version=comp[\"version\"])\n    # Add edges from dependency relationships\n    for dep in sbom.get(\"dependencies\", []):\n        for child in dep.get(\"dependsOn\", []):\n            G.add_edge(dep[\"ref\"], child)\n    return G\n```\n\nTransitive dependency analysis identifies components that are not directly included but are pulled in through dependency chains. A vulnerability in a deeply nested transitive dependency (e.g., 4 levels deep) still represents risk but may be harder to remediate.\n\nKey graph metrics for risk assessment:\n- **In-degree**: How many components depend on this one (high in-degree = high blast radius)\n- **Shortest path to root**: Distance from application entry point (closer = more exploitable)\n- **Betweenness centrality**: Components that sit on many dependency paths (bottleneck risk)\n\n### Step 5: Calculate Risk Scores\n\nAggregate vulnerability data into component and overall risk scores:\n\n```\nRisk Score Calculation:\n━━━━━━━━━━━━━━━━━━━━━━\nComponent Risk = max(CVSS scores of all CVEs affecting the component)\n\nWeighted Risk = Component Risk * Dependency Factor\n  where Dependency Factor = 1.0 + (0.1 * in_degree)\n  (more dependents = higher organizational impact)\n\nOverall SBOM Risk = weighted average of all component risks\n  weighted by dependency centrality\n\nRisk Levels:\n  CRITICAL: CVSS >= 9.0 or known exploited (CISA KEV)\n  HIGH:     CVSS >= 7.0\n  MEDIUM:   CVSS >= 4.0\n  LOW:      CVSS \u003C 4.0\n```\n\n### Step 6: Cross-Validate with Grype\n\nUse grype to independently scan the SBOM and compare findings:\n\n```bash\n# Scan CycloneDX SBOM with grype\ngrype sbom:sbom-cyclonedx.json -o json > grype-results.json\n\n# Scan SPDX SBOM\ngrype sbom:sbom-spdx.json -o table\n\n# Filter by severity\ngrype sbom:sbom-cyclonedx.json --only-fixed --fail-on critical\n```\n\nGrype pulls vulnerability data from NVD, GitHub Security Advisories, Alpine SecDB, Red Hat, Debian, Ubuntu, Amazon Linux, and Oracle security databases, providing broader coverage than NVD alone.\n\n### Step 7: Generate Compliance Report\n\nProduce a structured report suitable for regulatory compliance:\n\n```\nSBOM VULNERABILITY ANALYSIS REPORT\n====================================\nSBOM File:         app-sbom-cyclonedx.json\nFormat:            CycloneDX v1.5\nAnalysis Date:     2026-03-19\nTotal Components:  247\nTotal Dependencies: 1,842 (direct: 34, transitive: 213)\n\nVULNERABILITY SUMMARY\n  Critical:  3 components \u002F 5 CVEs\n  High:      11 components \u002F 18 CVEs\n  Medium:    27 components \u002F 41 CVEs\n  Low:       8 components \u002F 12 CVEs\n\nCRITICAL FINDINGS\n1. lodash@4.17.20\n   CVE-2021-23337 (CVSS 7.2) - Command Injection via template\n   CVE-2020-28500 (CVSS 5.3) - ReDoS in trimEnd\n   Dependents: 14 components (high blast radius)\n   Fix: Upgrade to 4.17.21+\n\n2. log4j-core@2.14.1\n   CVE-2021-44228 (CVSS 10.0) - Log4Shell RCE [CISA KEV]\n   CVE-2021-45046 (CVSS 9.0) - Incomplete fix bypass\n   Dependents: 8 components\n   Fix: Upgrade to 2.17.1+\n\nDEPENDENCY GRAPH RISKS\n  Most depended-on: core-util@1.2.3 (47 dependents)\n  Deepest chain: app -> framework -> adapter -> codec -> zlib (5 levels)\n  Bottleneck components: 3 components on >50% of dependency paths\n\nLICENSE COMPLIANCE\n  Copyleft licenses found: 2 (GPL-3.0 in libxml2, AGPL-3.0 in mongodb-driver)\n  Review required for commercial distribution\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **SBOM** | Software Bill of Materials; a formal inventory of all components, libraries, and dependencies in a software product |\n| **CycloneDX** | OWASP-maintained SBOM standard supporting JSON, XML, and protobuf formats with dependency graph and vulnerability data |\n| **SPDX** | Linux Foundation SBOM standard focused on license compliance with support for package, file, and snippet-level detail |\n| **PURL** | Package URL; a standardized scheme for identifying software packages across ecosystems (e.g., pkg:npm\u002Flodash@4.17.21) |\n| **CPE** | Common Platform Enumeration; NIST naming scheme for IT products used to correlate with NVD CVE data |\n| **NVD** | National Vulnerability Database; US government repository of vulnerability data indexed by CVE identifiers |\n| **Transitive Dependency** | A dependency not directly declared but pulled in through the dependency chain of direct dependencies |\n| **CISA KEV** | CISA Known Exploited Vulnerabilities catalog; CVEs confirmed to be actively exploited in the wild |\n\n## Tools & Systems\n\n- **syft** (Anchore): Open-source SBOM generator supporting 30+ package ecosystems and CycloneDX\u002FSPDX output\n- **grype** (Anchore): Vulnerability scanner that accepts SBOMs as input and correlates against multiple advisory databases\n- **cyclonedx-python-lib**: Python library for creating, parsing, and validating CycloneDX SBOMs programmatically\n- **lib4sbom**: Python library for parsing both SPDX and CycloneDX format SBOMs\n- **nvdlib**: Python wrapper for the NVD 2.0 API supporting CVE and CPE queries with rate limit management\n- **OWASP Dependency-Track**: Platform for continuous SBOM analysis, vulnerability tracking, and policy enforcement\n\n## Common Scenarios\n\n### Scenario: Assessing Vendor Software After Log4Shell Disclosure\n\n**Context**: After the Log4Shell (CVE-2021-44228) disclosure, the security team needs to determine which vendor-supplied applications contain vulnerable versions of log4j. Several vendors have provided SBOMs per contractual requirements.\n\n**Approach**:\n1. Collect all vendor SBOMs (CycloneDX or SPDX JSON format)\n2. Parse each SBOM and search for log4j-core components with versions \u003C 2.17.1\n3. Query NVD API for the specific CVEs (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105)\n4. Build dependency graphs to identify which application components depend on log4j\n5. Calculate blast radius: how many services and endpoints are exposed\n6. Generate prioritized remediation report sorted by exposure and business criticality\n7. Cross-validate findings with grype scan of the same SBOMs\n\n**Pitfalls**:\n- Vendor SBOMs may be incomplete, missing shaded\u002Fbundled JAR files that embed log4j\n- SPDX and CycloneDX version differences may affect parser compatibility\n- NVD API rate limits can slow analysis when scanning hundreds of components without an API key\n- CPE names in SBOMs may not exactly match NVD entries, requiring fuzzy matching\n- Transitive dependencies may include log4j even when it is not a direct dependency\n",{"name":5,"tags":24,"author":34,"domain":35,"license":14,"version":36,"nist_csf":37,"subdomain":42,"description":43,"nist_ai_rmf":44,"mitre_attack":50,"atlas_techniques":55},[25,26,27,28,29,30,31,32,33],"SBOM","CycloneDX","SPDX","NVD","CVE","supply-chain","dependency-analysis","syft","grype","mukul975","cybersecurity","1.0.0",[38,39,40,41],"GV.SC-01","GV.SC-03","GV.SC-06","GV.SC-07","supply-chain-security","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\u002FSPDX parsing, or CVE correlation.\n",[45,46,47,48,49],"GOVERN-5.2","MAP-1.6","MANAGE-2.2","GOVERN-1.1","GOVERN-4.2",[51,52,53,54],"T1195.001","T1195.002","T1554","T1190",[56],"AML.T0010","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-sbom-for-supply-chain-vulnerabilities",{"tool":69,"command":70},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-sbom-for-supply-chain-vulnerabilities",{"tool":72,"command":73},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill analyzing-sbom-for-supply-chain-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities\u002FSKILL.md",true,[77,81,87],{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",6060,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fagent.py","SCRIPT","脚本",28406,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fanalyzing-sbom-for-supply-chain-vulnerabilities\u002Fscripts\u002Fagent.py",[94,102,109,116,123,130],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]