Oracle 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
Oracle here refers to PDF output from Oracle E-Business Suite, BI Publisher, and other Oracle enterprise reporting components that emit PDFs server-side.
Oracle-produced PDFs are server-rendered institutional documents. Low signal for tampering on their 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 Oracle in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 6 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Oracle writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.4 (68% of files where Oracle is the Producer).
Oracle sits upstream in 83% of cases — read this row as “what kinds of documents end up routed through Oracle.”
Related profiles
Other tools that frequently share metadata with Oracle in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Oracle 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.