Technology fingerprinting

Library Reference

These are the client-side packages we can recognize on your site, each tied to the latest published release on the public npm registry where applicable. During a scan, we compare what we detect in the page with these reference versions to flag outdated scripts and styles. If the registry hasn’t synced yet, we fall back to bundled reference data.

Last registry sync:

Library npm package Reference latest Latest release (npm) Status Notes
Alpine.js alpinejs 3.17.4 Active —
Angular — 19.0.0 — Active Scanner matches Angular HTML patterns; npm uses @angular/core with different numbering.
anime.js animejs 4.5.0 Active —
AOS (Animate On Scroll) aos 2.3.4 Active —
Axios axios 1.20.0 Active —
Bootstrap bootstrap 5.3.8 Active —
Chart.js chart.js 4.5.1 Active —
core-js core-js 3.50.0 Active —
D3.js d3 7.9.0 Active —
Day.js dayjs 1.11.23 Active —
Font Awesome @fortawesome/fontawesome-free 7.3.1 Active —
GSAP gsap 3.15.0 Active —
Handlebars handlebars 4.7.10 Active —
htmx htmx.org 2.0.11 Active —
jQuery jquery 4.0.0 Active —
jQuery UI jquery-ui 1.14.2 Active —
Lit lit 3.3.3 Active —
Lodash lodash 4.18.1 Active —
Lottie (lottie-web) lottie-web 5.13.0 Active —
Marked (Markdown) marked 18.1.1 Active —
Moment.js moment 2.31.0 EOL risk Project in maintenance mode; consider dayjs or luxon.
Popper.js @popperjs/core 2.11.8 Active —
Preact preact 11.0.1 Active —
Prism.js prismjs 1.30.0 Active —
React react 19.3.0 Active —
Socket.IO client socket.io-client 4.8.4 Active —
Svelte svelte 5.57.2 Active —
Swiper swiper 14.3.0 Active —
Tailwind CSS tailwindcss 4.3.3 Active —
Three.js three 0.186.1 Active —
Underscore.js underscore 1.13.8 Active —
Video.js video.js 8.24.1 Active —
Vue.js vue 3.5.43 Active —

How Versions Stay Current

  • When you run a scan, we check whether our cached “latest” versions from the public npm registry are still fresh. If the cache is older than about six hours, we refresh it in the background—you may briefly see a refreshing library versions step on the progress bar.
  • Each row pairs a detected library with the npm package we use for version checks. We maintain this catalog as part of the service; live registry data is merged in when available, and we fall back to bundled references if the registry can’t be reached so your scan still finishes.