Where does this data come from?

For each CVE, the upstream fix commit is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Only real patches count: release ranges, version bumps, manifests and test files are excluded.

Why can one CVE count several functions?

A fix is counted once per function it changes. A patch that edits three functions appears under each of them, and a function changed by several CVEs lists every one of them.

RadicalNotion.AI

Log in Create an account

Patched functions

The functions, files and repositories that CVE fixes change, read from the upstream patch of each CVE.

0

Repositories

0

CVEs with a located fix

0

Functions patched

0

Patch hunks

Repositories with the most located fixes

Ranked by the number of published CVEs whose fix was traced to functions in the repository.

Functions patched by the most CVEs

The same function fixed again and again, across every repository.

Frequently asked questions

Where does this data come from?: For each CVE, the upstream fix commit is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Only real patches count: release ranges, version bumps, manifests and test files are excluded.
Why can one CVE count several functions?: A fix is counted once per function it changes. A patch that edits three functions appears under each of them, and a function changed by several CVEs lists every one of them.