logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.49.0

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · [email protected] · Made in Finland

Status

Algorithm v2.49.0

Tool profile

BIRT Report Engine

BIRT Report Engine 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 statistics
Forensic verdict

Mixed signal

Based on this tool’s share of the HTPBE? corpus.

Modification rate
55%+6pp above baseline
Corpus baseline: 49%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
55%
+6pp above baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How BIRT Report Engine shows up in HTPBE? corpus

BIRT Report Engine is one of the PDF-handling tools surfaced in the HTPBE? corpus. BIRT Report Engine appears predominantly as the original Creator (100% of its occurrences) — i.e. on documents that started life inside BIRT Report Engine rather than passing through it as a downstream re-saver.

HTPBE? reads the BIRT Report Engine 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 BIRT Report Engine acts as Creator, 55% carry modification markers; on documents where it acts as Producer, 0% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against BIRT Report Engine or its users.

The signal
HTPBE? reads the BIRT Report Engine 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.

Reading guide

How to read this page

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 BIRT Report Engine 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.

Caveats

  • Only 11 files list BIRT Report Engine, so every percentage here moves a lot with each additional file.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of BIRT Report Engine.
  • Submitted files lean towards documents that someone wanted checked, so rates here can sit higher than in everyday document flows.
  • Metadata can be rewritten by anyone, so a producer name on its own is never treated as proof either way.
Read a PDF’s metadata for freeAll tool statisticsCreator vs Producer explainedPDF metadata fields referenceCheck PDFs through the API

Role in the workflow

How BIRT Report Engine shows up in metadata

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.

CAs Creator · 100%
As Producer · 0%P
CAs creator
  • Share of appearances
    100%
  • Modification rate
    55%
  • Avg file size
    41 KB
PAs producer
  • Share of appearances
    0%
  • Modification rate
    0%

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the final file, which is not always the same software.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Name fingerprints

Also goes by

Different version strings and spellings observed for BIRT Report Engine in the wild. All are merged into the same canonical profile.

BIRT Report Engine /content/XTMS_WAR.war/WEB-INF/lib/org.eclipse.birt.runtime-4.6.0.jar.54.5%
Workday BIRT Report Engine, version: 4.7.036.4%
BIRT Report Engine /apps/saintsid/9090/ReportEngine/lib/org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar using iText /apps/saintsid/9090/ReportEngine/lib/org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar.9.1%

Why variants matter

The same tool publishes itself under 3 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.

Most common
BIRT Report Engine /content/XTMS_WAR.war/WEB-INF/lib/org.eclipse.birt.runtime-4.6.0.jar.
54.5% of appearances
Variant spread
3 distinct strings
Long-tail share: 45.5%
Observed range
09.12.2022 → 08.10.2026

Related profiles

Tools you’ll see next to BIRT Report Engine

Other tools that frequently share metadata with BIRT Report Engine in the same documents. Each card links to its own forensic profile.

P73% co-occurrence
iText
Corpus share7.3%
Mod rate48%

Long tail

Notable observations

Smaller cuts of the BIRT Report Engine corpus – useful context, but treat each row as a single data point rather than a strong signal.

Avg pages per document
1.1
Oldest observed
09.12.2022 — almost 4 years ago

FAQ

BIRT Report Engine in PDF metadata: common questions

What is BIRT Report Engine?

BIRT Report Engine is a PDF-handling tool that writes its name into the Creator or Producer field of the PDFs it generates or re-saves.

Why does BIRT Report Engine appear in the metadata of a PDF?

A PDF can record the software that created it (Creator) and the software that last wrote the file out (Producer). When BIRT Report Engine generated the file, or re-saved it, it can leave its name in one of those fields. The field is filled in by software, not checked by anyone, so it is a hint about the file’s history rather than a guarantee.

Does BIRT Report Engine in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many BIRT Report Engine files are original output, and a file that was edited can name any tool at all. What matters is the whole picture: how the file is built, how its dates and structure line up, and whether the Creator and Producer fit together.

How should I read the BIRT Report Engine statistics?

The figures describe the 11 files in the HTPBE? corpus that list BIRT Report Engine as Creator or Producer. The modification rate is the share of those files that carry modification markers. It is a base rate for this particular set of files, not a property of BIRT Report Engine and not a prediction for any single document.

Can I compare BIRT Report Engine with other tools using these numbers?

Only loosely. The corpus consists of PDFs people chose to submit for checking, which skews towards documents someone had a reason to doubt. A tool popular for legitimate bulk output can still show a high rate here, and a rarely seen tool can show an extreme rate from a handful of files. These pages are not a quality ranking of the tools themselves.

How do I check a PDF that lists BIRT Report Engine?

Upload it to HTPBE? for a modification check, or open it in the free PDF Metadata Viewer to see the Creator, Producer and dates stored in the file. The same check is available through the HTPBE? API.

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.

Start Free – Close the Structural Fraud GapSee Pricing
Read API Docs →