Download websites that use qiankun

About qiankun

A large internal application is rarely built by one team, and the browser offers those teams no natural seam. Server code splits into services that deploy on their own schedules, but a page loaded from one origin has a single global namespace, a single set of styles and a single runtime, so two teams shipping into it are sharing a room whether they meant to or not. Micro-frontend shells exist to draw a line down the middle of that room.

qiankun is one of those shells, published by Ant Group under the MIT license, written in JavaScript and dated in our records to 2019. The library loads independently built applications into a host page, gives each a sandboxed execution context so their globals do not collide, isolates their styles and manages their lifecycles.

As of October 2026 we detect it on 29 sites, and that figure deserves more skepticism than most. Applications assembled this way are typically operations consoles, admin panels and staff portals, which is to say precisely the parts of a company's web estate that sit behind a login and are never crawled. Public detection sees the sign-in screen at best. Our number should be read as the visible tip of a pattern whose real weight is inside organizations rather than on their marketing sites.

Version data adds a little more. A narrow spread of that kind is what you would expect from a dependency pinned during the initial build of a platform and then left alone, because a shell is load-bearing and upgrading it means retesting every application it hosts. Anyone tracking maintenance risk in front-end infrastructure will read a tight cluster as evidence that upgrades are rare, not that everyone is current.

The audience for the file is narrower than for a consumer framework and correspondingly more motivated. Vendors selling developer tooling, testing platforms and observability into large engineering organizations want to know which companies build this way. Security researchers want a population of sites that rely on a sandbox for isolation. Consultancies doing platform migrations want it because the presence of a micro-frontend shell describes the shape of a client's engineering organization before the first meeting.

A per-domain check answers a curiosity. The downloadable list answers a structural question, which organizations have committed to composing applications this way, what else runs alongside the shell on their public sites, and whether the pattern is spreading or settling, and no query taken one domain at a time will show you that.