Source
Dependencies (SCA), licences & secrets — found from sitemap — Semgrep
Checked for Semgrep on 6 Nov 2026
- Page
- https://docs.semgrep.dev/semgrep-supply-chain/sbom
- Checked
- 6 Nov 2026, 17:02 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e39203a0d956330de8241677767f52d986f47f879ffd73e836b8f0b788c07f0c
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Sbom generation Report an error
“Semgrep Supply Chain (SSC) can generate an SBOM for each repository you have added to Semgrep AppSec Platform.”
-
Sbom data sources Report an error
“The vulnerability information from the default branch for the project The dependency information from the latest full scan for the project.”
-
Sbom formats Report an error
“CycloneDX 1.4 JSON CycloneDX 1.4 XML CycloneDX 1.5 JSON CycloneDX 1.5 XML CycloneDX 1.6 JSON CycloneDX 1.6 XML CycloneDX 1.7 JSON CycloneDX 1.7 XML”
-
Sbom branch caveat Report an error
“if your workflow differs and you run full scans on non-primary branches, this can create a mismatch between dependencies and vulnerabilities in the generated SBOM. To avoid the mismatch, ensure that the latest full scan runs on the primary branch of the repository”
-
Sbom vulnerability fields Report an error
“Semgrep provides additional metadata in the vulnerabilities field. Nested under the vulnerabilities field is a list of data objects describing a specific vulnerability.”
-
Sbom advisories field Report an error
“Advisories Links to GitHub or NIST advisories about the specific vulnerability.”
-
Sbom reachability analysis field Report an error
“Analysis Semgrep’s analysis of this vulnerability in your supply chain. Under analysis are state and justification fields, which describe if your codebase is affected by the vulnerability and why Semgrep thinks it is or is not affected.”
-
Sbom ratings field Report an error
“Ratings Semgrep Supply Chain’s severity rating of this vulnerability.”
-
Sbom references field Report an error
“References Links to the specific CVE. References can come from NIST, Electron release notes, and GitHub Security Advisory.”
-
Sbom cwes field Report an error
“CWEs The assigned CWE (common weakness enumeration) number.”
-
Sbom prerequisite Report an error
“At least one repository that scans for dependencies through Semgrep Supply Chain. See Scan third-party dependencies.”
-
Sbom tools field Report an error
“Tools Details about Semgrep, the tool used to generate the SBOM.”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Application Security Engineer Dependencies (SCA), licences & secrets
- The Engineering Manager Dependencies (SCA), licences & secrets
- The Lead Developer Dependencies (SCA), licences & secrets
- The Platform Engineer Dependencies (SCA), licences & secrets
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Skeptic Dependencies (SCA), licences & secrets