OpenPDF appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.
Back to all statisticsForensic verdictBased on 494 appearances across the HTPBE? corpus.
Corpus profile
OpenPDF is the open-source fork of an early iText line, used as a Java PDF library for both generating and modifying PDFs.
OpenPDF appears across legitimate generation and re-save workflows. When it is the latest Producer on a document whose Creator was institutional, the producer/creator mismatch is a contextual signal.
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 OpenPDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 11 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions OpenPDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.5 (100% of files where OpenPDF is the Producer).
JasperReports sits upstream in 64% of cases — read this row as “what kinds of documents end up routed through OpenPDF.”
Related profiles
Other tools that frequently share metadata with OpenPDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the OpenPDF 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.