Download websites that use AngularJS

About AngularJS

A framework that has reached the end of its life stops being a technology decision and becomes an inventory problem. Google has ended support for AngularJS, which means no further security patches and no upstream fixes, and every remaining installation is a choice somebody made once and has not revisited since. Detecting it is therefore less about knowing how a site was built and more about knowing what condition it is in now.

The framework deserves its place in history. Released in 2010 under MIT and written in JavaScript, it brought declarative templates, dependency injection and automatic synchronisation between model and view to mainstream web development, and for most of a decade it was the default answer for teams building application style interfaces in the browser. Its successor from the same vendor is a full rewrite with a different architecture, which is exactly why so many of the original applications were never migrated. Moving is not an upgrade, it is a rebuild, and rebuilds need a budget.

Evidence for that stalling shows up in the version data. Across the detected sites we record 158 distinct versions, clustered around 1.2.28. A dependency under active maintenance narrows over time as updates roll out, while an abandoned one fans out and stays fanned out, each site frozen at whatever release was current on the day work stopped. A spread of that width in one library is a fair description of a population that is no longer being tended.

Geography adds the commercial layer. As of October 2026 the framework appears on 86,933 sites, with 17,834 attributed to United States and .com leading the domain endings, which reflects where enterprise and startup engineering teams were building heavily during its peak years. Long lived business applications, internal tools exposed to the web, dashboards and customer portals are all over represented in this kind of population, and those are precisely the applications that are expensive to replace and therefore likely to persist.

Several audiences buy exactly this list. Security vendors want unpatched framework installs because an unsupported client side framework is a durable finding in any assessment. Consultancies selling modernisation want the same rows for the opposite reason, since a site frozen on an old release is a qualified rebuild opportunity with a self evident business case. Supply chain and inventory teams want the population to check their own vendors and partners against it.

Detection limits are real and worth naming. Version strings are read from file paths and runtime globals, so a site that bundles and minifies the framework into a single application file can lose both the version and, in some cases, the framework marker entirely, which pushes the count down. Some pages load the library while barely using it, a leftover from a widget or an admin screen, so presence does not always mean the application core depends on it.

A per domain lookup tells you one site's answer. The downloadable population tells you how large the unmaintained estate is, how it distributes across versions, countries and hosting, what else those sites run, and how quickly it is shrinking between releases. Those are the only questions worth asking about a technology whose remaining story is its decline.