How Basely compares
Each image's package database is read straight from its layers over the registry API, for {{PLATFORM}}, and every package is looked up in OSV: OS packages against the distro's own advisory feed, so backported fixes count as fixed, and the language packages the image ships (pip, npm, Go, Maven, gems) against theirs. Advisories the distro marks as unimportant or negligible, Chainguard false positives, kernel advisories (a container runs on the host's kernel) and anything an image's VEX rules out are left out.
Images are ranked by severity-weighted advisories, then size. A candidate that would break a stage, such as one with no shell under a stage with RUN steps, is never the recommendation; it can be offered as worth the changes when it at least halves the risk. Counts cover what the base image ships, not what your build installs on top.