Repository navigation
Let a pluggable vulnerability source drive updates, not only OSV #47580
august-monitor
started this conversation in
Suggest an Idea
Replies: 1 comment
|
Thanks! This is actually already planned 😉 #40048 is the planned work that will enable this, and the framework will provide the means to drive custom sources of vulnerability data (among other things) into Renovate |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Tell us more.
We run self-hosted Renovate against our repositories, and separately run
owasp-depscanon the same repositories and push the SBOM and VEX into Dependency-Track.osvVulnerabilityAlertsis on too. A dependency can end up flagged by our own scanner and untouched by Renovate, or the other way round. The two draw from different vulnerability data.I read through
lib/workers/repository/process/vulnerabilities.tsat commit01e87b7before asking here. TheVulnerabilitiesclass queries@renovatebot/osv-offlinedirectly throughthis.osvOffline.getVulnerabilities. It maps each manager's datasource to an OSV ecosystem throughdatasourceToOsvEcosystem. It parses CVSS vectors inevaluateCvssVector. It writes PR body text ingeneratePrBodyNotes, using OSV's own advisory id prefixes to decide the reference links. There is no seam in that file for a second source to feedvulnerabilityToPackageRules.Is this a idea that someone else find interesting? If there were something like this, we would use it with DependencyTrack.
All reactions