Apache FOP reads as a institutional generator — its modification rate in our corpus does not sit meaningfully above the baseline. The name alone is never the verdict; each file is judged on its own structure.
Back to all statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
Apache FOP renders XSL-FO into PDF and is a common back-end for enterprise document generation pipelines (banking, telecom, government).
FOP output comes from XSL-FO templates in enterprise document pipelines. HTPBE? reads it alongside every other layer of the file.
Reading guide
Every PDF stores two software labels: the Creator, which names the application that first produced the document, and the Producer, which names the software that last wrote the file out. This page counts the files HTPBE? has analysed where Apache FOP fills one of those labels, and shows how often those files carry modification markers, which PDF versions they use and which other tools sit next to them.
A tool name tells you where a file passed through, not whether anyone changed its content. A Creator and Producer that agree usually point to a single pass; a Producer that differs from the Creator means the file was written out again by another program, which has many ordinary explanations such as compression, merging or a print-to-PDF step.
Role in the workflow
Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.
Name fingerprints
Different version strings and spellings observed for Apache FOP in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 14 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Apache FOP writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (95% of files where Apache FOP is the Producer).
Apache FOP sits upstream in 98% of cases — read this row as “what kinds of documents end up routed through Apache FOP.”
Related profiles
Other tools that frequently share metadata with Apache FOP in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Apache FOP corpus – useful context, but treat each row as a single data point rather than a strong signal.
FAQ
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.