Apache FOP reads as a institutional generator — its modification rate sits at or below the corpus baseline, consistent with single-pass institutional output.
Back to all statisticsForensic verdictBased on 635 appearances across 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 appears on first-generation XSL-FO renders. Low signal in tampered corpus on its own.
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 10 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 (99% 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.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.