Updated 03:00
Determinate Secure Packages CVE Remediation Dashboard
Every CVE (Common Vulnerabilities and Exposures record) in Determinate Secure Packages has a fix deadline determined by our service-level agreement (SLA). See how Determinate Secure Packages stays ahead of CVEs.
Fixed within SLA
933
last 30 days
Fixed within SLA
44
last 7 days
Open
82
not yet fixed but still within SLA
Overdue
0
open
Missed SLA
0
last 30 days
Currently tracked CVEs
Every dot is one currently tracked CVE, with a color and shape indicating its current status, and placed in the row that corresponds to its severity and the position on the x-axis that corresponds to the day of its SLA deadline. The vertically aligned dotted purple lines indicate SLA dates for the corresponding severity.
52 of 516 tracked CVEs shown.
- Open (52)
- Today
- SLA deadline for a CVE published today
About Determinate Secure Packages
Every fix on this page is one you didn't have to make. Determinate Secure Packages watches the packages you depend on, patches them within the SLA, and ships the builds to you.
Determinate Secure Packages overview
What you get, how it fits your Nix setup, and how to start.
determinate.systems (opens in a new tab)
Documentation
How the SLA works, which packages we cover, and how to use them.
docs.determinate.systems (opens in a new tab)
Supply chain security
Control over the code, dependencies, builds, and environments behind every system you run.
determinate.systems (opens in a new tab)
Make CVE remediation our job, not yours.
Tell us what you run. We'll show you what Determinate Secure Packages covers, how the SLA applies, and how to get started.
Vulnerability databases
The databases the dashboard draws on. Every CVE here is one of theirs.
- National Vulnerability Database (opens in a new tab)
The CVE records the dashboard follows and the write-up each one shows.
- Open Source Vulnerabilities (opens in a new tab)
A second record of each CVE with the affected versions.