Crystal Reports appears on both unmodified and modified documents in our corpus. 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
Crystal Reports is one of the PDF-handling tools surfaced in the HTPBE? corpus. Crystal Reports splits its occurrences between Creator (56%) and Producer (44%) roles, meaning it sometimes originates documents and sometimes re-emits them after another tool created them.
HTPBE? reads the Crystal Reports name as one input among many and weighs it together with the rest of the file’s structure – the tool itself is never the accusation.
On documents where Crystal Reports acts as Creator, 48% carry modification markers; on documents where it acts as Producer, 38% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against Crystal Reports or its users.
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 Crystal Reports 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 Crystal Reports in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 2 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Crystal Reports writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.7 (71% of files where Crystal Reports is the Producer).
Related profiles
Other tools that frequently share metadata with Crystal Reports in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Crystal Reports 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
FAQ
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.