Download websites that use phpDocumentor

About phpDocumentor

What gets detected here is output rather than infrastructure. phpDocumentor runs on a developer machine or inside a build pipeline, reads PHP source together with the comment blocks in it, and writes static HTML. Nothing about the tool serves traffic. A site is recorded as carrying it because somebody published the generated documentation to a web host and the generated pages announce what produced them.

The distinction changes every question worth asking about the number. A count of detections is a count of published documentation sets, not a count of projects using the tool. Most runs never leave a repository or a build job, and projects that do publish often push the output to a hosting service under a shared domain, where a domain-level index records the host and not the project. As of October 2026 the fingerprint stands at 1 in our data, and the figure should be read as publicly reachable published documentation, which is a narrow slice of real usage and known to be narrow.

The narrow slice is still worth having, because of what it identifies. A domain hosting generated PHP interface documentation belongs to a library, a framework, an agency or an engineering team maintaining PHP code seriously enough to document it. Developer tool vendors, package registries, technical recruiters and anyone mapping a language ecosystem are looking for that population, and it is not easy to assemble from search alone.

phpDocumentor has been around since 2000 and is distributed under an MIT licence with no company behind it, the ordinary arrangement for tooling of its generation. Longevity carries a measurement side effect worth flagging. Output produced by very old versions looks different from output produced by current ones, so a detection rule tuned to recent templates will miss the archives, and documentation sites are routinely abandoned in place. A published page can outlive the project it documents by a long stretch.

Against all that, the export earns its place through scale and adjacency. A per-domain lookup tells you that a particular documentation site was generated with this tool. The export tells you how many domains publish PHP documentation of this kind at all, what web servers and hosting they sit on, which other developer facing technologies they carry, and whether the set is growing as new projects publish or shrinking as old ones vanish. Reading a language ecosystem from the outside means counting artefacts, and generated documentation is one of the few artefacts a public crawl can see directly.