Nova Platform · Packages and security
Am I affected?
Nova Platform captures the packages in your project automatically and tells you what is known, what is likely and what has not been assessed.
Capture
No reports
to upload.
Packages, their dependencies and security information are captured from ordinary supported runs. You do not locate, upload or load report files. Open Packages and the inventory for your project is there.
Each inventory is tied to the run that produced it. If an inventory is larger than the platform can analyze, it says so instead of showing a shortened or empty result.
The answer
Four facts, kept separate.
A match in an advisory database is not the same as being exploitable, and no findings is not the same as safe. Nova Platform shows each fact on its own.
Matches
Which captured packages and versions match a published advisory.
Exposure evidence
Whether the package is on a runtime path, including through transitive dependencies.
Coverage
Which packages were assessed and which were not, stated explicitly.
Uncertainty
What the available evidence cannot establish. Missing analysis is never shown as a clear result.
In the product
From package to affected service.
Advisory matching
Captured packages are matched against OSV advisory data. The advisory mirror refreshes automatically.
Installed systems
The platform observes what is installed on your running systems, not only what a build produced.
Service impact
Findings are linked from a package to the services that use it, so you can see what is affected.
Priorities on Systems
Each service shows its advisory priorities, with the exact evidence one click away.
Reading order
The important
cards come first.
Packages lists advisory-bearing packages first and shows which inventory you are looking at while it loads. Expand a finding to read its evidence.