Skip to content

Security

How to find outdated front-end libraries on my site

Versions this old are out of support and have published XSS advisories against them. Detection is from the filename, so a file renamed without its version is invisible to this check — and a bundled copy is invisible too.

What 13x checks

This is rule security.outdated-libraries in the public registry: No known-outdated front-end libraries. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Security
Score weight
6 of the readiness score
Scope
Runs on every audited page
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Outdated libraries in use: .

These versions are out of support and have published XSS advisories against them. Upgrade, or drop the dependency — a jQuery still on the page for one selector call is worth removing rather than upgrading.

bash code
npm audit
npx npm-check-updates -u && npm install

Two caveats on this check: it reads the version from the filename, so a file renamed without its version is invisible here, and a bundled copy inside your application code is invisible too. npm audit covers what this cannot.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More security checks