JasperReports 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 this tool’s share of the HTPBE? corpus.
Corpus profile
JasperReports is an open-source server-side reporting engine widely used inside Java enterprise applications to render statements, invoices, and regulatory documents from templates.
Jasper-produced PDFs are template-rendered institutional output. Low signal on its own; what matters is whether the same document also carries traces of an unrelated downstream editor.
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 JasperReports in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 25 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions JasperReports writes when acting as Producer, and the other tools that appear in the same documents.
Related profiles
Other tools that frequently share metadata with JasperReports in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the JasperReports corpus — useful context, but treat each row as a single data point rather than a strong signal.
Of files carry at least one digital signature
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.