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

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

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.23.1

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland 🇫🇮

Status

Algorithm v2.23.1

Tool profile

react-pdf

react-pdf 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 statistics
Forensic verdict

Mixed signal

Based on 15 appearances across the HTPBE? corpus.

Modification rate
13%-35pp below baseline
Corpus baseline: 48%
Total appearances
15
0.10% of corpus
Modification rate
13%
-35pp below baseline
Role split
60%C/40%P
Creator vs Producer share of appearances

Corpus profile

How react-pdf shows up in HTPBE? corpus

react-pdf is a React-based PDF generator used in modern SaaS apps to build PDFs from React components.

Often the original generator on React-stack outputs. Contextual signal arises only when its appearance breaks the expected creator/producer pairing.

The signal
Often the original generator on React-stack outputs.

Role in the workflow

How react-pdf 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 · 60%
As Producer · 40%P
CAs Creator
  • Usage
    9
  • Modification rate
    22%
  • Avg file size
    1006 KB
PAs Producer
  • Usage
    6
  • Modification rate
    0%
  • Avg file size
    1.4 MB

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the bytes — and is the field that gets overwritten when a PDF is opened, edited, and saved by a downstream tool.

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.

Distributions

What ships alongside react-pdf

The PDF versions react-pdf writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.3 (100% of files where react-pdf is the Producer).

PDF 1.3100.0%

Common Producers when react-pdf is the Creator

pdfcpu writes 22% of these files — that pairing is the Adobe-stack default for many institutional pipelines.

pdfcpu22.2%
Acrobat Distiller11.1%

Related profiles

Tools you’ll see next to react-pdf

Other tools that frequently share metadata with react-pdf in the same documents. Each card links to its own forensic profile.

P13% co-occurrence
pdfcpu
Appearances2
Mod rate50%
P7% co-occurrence
Acrobat Distiller
Appearances303
Mod rate55%

Long tail

Notable observations

Smaller cuts of the react-pdf corpus — useful context, but treat each row as a single data point rather than a strong signal.

Pages parsed
29
Oldest observed
24 Feb 2026 — 3 months ago

Secure your workflow

Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.

Start free — close the structural fraud gapSee pricing
Read API docs →