Download websites that use Scully

About Scully

A static site generator is a build time tool, which means it has usually finished its work and left the building before any visitor arrives. Scully pre-renders an Angular application into static HTML, and what a crawler sees is the residue of that process rather than the process itself: markers left in generated markup, plus the client side bundle that hydrates it. Detection of a generator is an inference from output, and that inference is weaker than detecting a server which announces itself in a response header.

The inference is still worth making, because Scully tells you something quite specific about a team. Reaching for a generator built around Angular means an organisation had already committed to Angular, written in TypeScript, and then hit the familiar wall of a single page application on public content: slow first paint and search engines served an empty shell. HeroDevs maintains the project under a MIT licence, with the first release dated to 2019. A domain in this set is running a framework heavy stack while caring about how that stack gets indexed, which is a narrower and more revealing profile than simply using Angular.

Version data on a build time tool is unusually noisy. We hold 14 distinct version strings for Scully, and the value carried in this record is 0.0.0. Generated output often reports a default or unset version rather than the release that actually produced the page, so the spread should be read as evidence that installations are not uniform, not as an upgrade audit you can act on directly.

As of October 2026 we see Scully on 146 sites. A population that size is small enough to work through by hand once you have it, and small enough that a per-domain lookup service is close to useless for finding it, because you cannot guess your way to a scattered set of domains spread across the whole web. Enumeration is the only practical route, and enumeration is exactly what a downloadable list provides.

Who benefits from the enumeration? Tooling vendors and consultancies whose product targets Angular teams, since the set is pre-qualified for shops running it in production on public sites. Maintainers and security teams who need to reach downstream users when an advisory lands on a build dependency. And anyone tracking whether the ecosystem's static rendering story is consolidating around something else, which shows up as domains leaving the set between exports rather than as anything you could observe on any single page.