Download websites that use JavaScript Infovis Toolkit

About JavaScript Infovis Toolkit

Drawing a treemap or a hyperbolic tree inside a browser once meant reaching for a plugin, and JavaScript Infovis Toolkit was one of the libraries that did it in plain JavaScript instead. Released around 2009 under the MIT licence, the toolkit handled treemaps, radial layouts, force directed graphs and space trees while the usual alternative was Flash. What makes it worth a page now is less what it draws than the fact that people stopped choosing it.

Our record names no vendor for the toolkit. What the project page offers is an open licence and a donation link rather than a commercial relationship, which is exactly the pattern that lets a library outlive its own popularity. A file gets copied into a project, it works, there is no support contract to cancel, and it stays. Later visualisation libraries took the audience, but nothing forced the existing installs off, because a chart that renders correctly generates no pressure to rewrite it.

Finding the toolkit on a site today usually dates the page rather than describing the business. Dashboards, university and research pages, documentation portals and internal tools exposed to the public web are the common contexts, and in most cases the surrounding code was written in the same period and has not been touched since. Presence works as a stratigraphic marker, putting a floor under how long the front end has gone unrewritten, which is a more reliable read than a copyright line in a footer.

As of October 2026 we still find JavaScript Infovis Toolkit on 223 sites. Detection relies on recognisable filenames and global objects, so a copy bundled and minified into a larger application will not register, while a file that is served but never executed will. The count should be read as an indication of where the library survives rather than as a precise inventory, and both errors are real.

The audience for the full list is the modernisation trade. Application security and asset inventory teams need to know where unmaintained front end code is still being served to the public, since an abandoned dependency receives no patches by definition. Agencies and platform teams selling rebuilds need candidate lists rather than anecdotes. Researchers tracking how long abandoned libraries persist need the whole population, because the shape of that decay curve is invisible from any single domain. A per site lookup tells you one page is old, while a downloadable list tells you what kind of organisation lets a page get that old.