Rudder

Currently we rely on dependency-check-maven which uses the CVE databse and tries to match maven packages based on CPEs which is not realiable.

We often get false positives (e.g. a chrome extension with the same name as a maven package).

The proper way to track vulnerabilities is to use a proper detection process, which is the goal of OSV (the format) / osv.dev (the database, synced from different sources includes Github advisories, which announces main vulnerabilities in the maven ecosystem).

We can try to use https://github.com/G-Rath/osv-detector to check pom.xml file for known vulnerabilities in osv.dev.