The safeguards map / 1.1 Code and dependencies
Ortelius
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
A platform that ingests SBOMs at build time and matches deployed components against OSV, tracking each vulnerability until it is remediated.
Where it sits
1.1 Code and dependencies (primary): Reads SBOMs at build time and matches the components deployed in each environment against OSV on a schedule, tracking each vulnerability until it is remediated.
It ingests your Software Bill of Materials (SBOM) at build time, matches your deployed components against the OSV vulnerability database every 15 minutes, tracks every CVE from the moment it is introduced into a release through every environment it reaches until it is remediated, and measures how long each step takes against your SLA targets.
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- software
- Used by
- those who make itthose who run it
- Runs
- at runtime
Handoffs
consumes Vulnerability status: OSV
Collector's note
The OpenSSF TAC table lists Ortelius at the sandbox stage under its Vulnerability Disclosures working group. It sits with SBOM-based dependency review (1.1), as Dependency-Track does.
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.