Download websites that use Tippy.js

About Tippy.js

Nobody sets out to build a website around a tooltip. Tippy.js is a JavaScript libraries written in JavaScript that positions small floating elements next to whatever they describe, and it usually arrives on a site as a dependency of something larger: a theme, an admin panel, a documentation generator, a charting widget. Presence therefore says less about a developer's taste than about the supply chain sitting above the developer.

As of September 2026 we detect the library on 64,624 sites. Released in 2017, the library is old enough to have been bundled into a generation of commercial templates and recent enough that many of those templates are still being sold today.

The version field is where the interesting part sits. We record 61 distinct version strings across the installed base, with 6 the series that recurs across a large part of it and a long tail of older builds behind it. A dependency that a site never chose directly is a dependency nobody schedules an upgrade for. Fragmentation of that width is normal for transitive front end packages, and fragmentation is exactly what makes the version column useful, because it separates sites whose front end is rebuilt from sites where the bundle was frozen on the day the theme was installed.

Two audiences ask about that split from opposite directions. Security and supply chain teams want to know which public sites still ship a given release of a small library, since front end dependencies are rarely inventoried anywhere the site owner can query. Component and tooling vendors want the inverse view, a map of sites that already accept a third party interface dependency and could plausibly accept theirs.

The MIT license shapes the base as much as anything technical. Nothing has to be bought, registered or phoned home, so adoption leaves no vendor record anywhere, and a crawl of the public web is the only place the population becomes visible. Geography follows the same logic rather than any national preference. United States carries 32,093 of the detections and .com is the suffix that recurs, which together describe where commercially hosted, English language templates are sold rather than where the library is liked.

Limits are worth stating plainly. Bundlers routinely inline a small library into one application file and strip the marker we match on, so builds produced by a modern toolchain drop out of the count entirely. Our figure should be read as sites where the library is identifiable, not as sites where it runs. Under-detection of that kind is not random either, because the builds it hides are the modern ones, which biases the visible population toward older and simpler sites and understates how much of the base is current.

None of this is answerable one domain at a time. A lookup tells you that a single site loads a tooltip library. The downloadable list tells you how a dependency spreads through templates, how long an old release survives after its replacement ships, and which populations of sites move together because they share an upstream.