Every check / known-vulnerable-code

Does the outside code your site loads have published weaknesses?

We identify the libraries your site loads and the version each one says it is, then ask OSV, the open advisory database, about each version.

How it decides

OSV gathers GitHub's advisories and the npm registry's. The check speaks up when a version has a published advisory, and rates it high when one is high or critical. The match is on the version string, which a build patched in place can keep, so it means the version has an advisory, not that you are exploitable.

Why it matters

The advisories come with published instructions, which is what makes them worth acting on: automated tools already use them.

In more detail

The usual fix is updating to a current version, often one line in a config file or one click in a plugin screen.

Who fixes it, and where it runs

Who usually fixes it
Whoever built your site
Which plan runs it
The Business plan
Proof you own the site
Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
Who it is about
An intruder
Listed under
Outside code your site runs
Its name in a report
known-vulnerable-code

See what the free scan finds

The free scan runs 62 checks on any address, and this is not one of them: it runs on the Business plan.