Download websites that use Axios

About Axios

An HTTP client is not a design decision so much as a reflex. Reaching for Axios is what a developer does on the way to the problem they actually sat down to solve, and the choice tends to be made once and never revisited.

Axios is a JavaScript libraries that wraps HTTP requests in a promise based interface, released in 2014 under the MIT license and used from browsers and from server side JavaScript alike. Almost any application that talks to an API needs code of this shape, so the decision to include Axios tells you very little on its own. The version string tells you a great deal.

As of September 2026 we detect Axios on 30,026 sites, and across those installations we record 118 distinct version strings. 0.19.2 is the one running through the set, and it belongs to the pre release era of the library rather than to anything current. A page still serving a build from that period has usually not been rebuilt since the day it went up, because the file was compiled once, uploaded, and never touched again.

United States accounts for 13,048 of the total, with .com as the common suffix. Geography matters less here than it does for a hosted platform, because a library like Axios travels with a framework tutorial rather than with a local market. What the country column is good for in this case is narrowing an audit to a jurisdiction.

Old HTTP client releases carry published advisories, and the ones that have mattered for Axios involve request forwarding and credentials leaking to redirect targets. A security team, an insurer pricing web exposure, or a vendor selling dependency scanning does not need to know whether one domain is affected. Checking a single domain is something a browser console can do in a minute. The question worth paying for is which domains across a whole market still serve an affected build, and that is a filter across a list rather than a request against one site.

Detection has a known bias worth stating. Axios is usually bundled and minified into an application chunk, and a bundled copy carries no recognisable file name, so the sites we can name are weighted toward the ones serving the library as a separate script from a public CDN or a vendor directory. The real footprint is larger than the count above, and the version we record comes from what the path or the banner comment says rather than from what the code actually is. Treat the export as a floor, and as a sample of one deployment style, which happens to be the style where an unrebuilt bundle tends to sit.