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

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

🇫🇮 Made in Finland

Product

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

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.14.0

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875

Status

Algorithm v2.14.0

Tool profile

ActiveReports

ActiveReports 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 549 appearances across the HTPBE? corpus.

Modification rate
100%+52pp above baseline
Corpus baseline: 48%
Total appearances
549
2.7% of corpus
Modification rate
100%
+52pp above baseline
Role split
61%C/39%P
Creator vs Producer share of appearances

Corpus profile

How ActiveReports shows up in HTPBE? corpus

ActiveReports is one of the PDF-handling tools surfaced in the HTPBE? corpus. ActiveReports splits its occurrences between Creator (61%) and Producer (39%) roles, meaning it sometimes originates documents and sometimes re-emits them after another tool created them.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when ActiveReports appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

On documents where ActiveReports acts as Creator, 100% carry modification markers; on documents where it acts as Producer, 100% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against ActiveReports or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when ActiveReports appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

Role in the workflow

How ActiveReports 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 · 61%
As Producer · 39%P
CAs Creator
  • Usage
    337
  • Modification rate
    100%
  • Avg file size
    364 KB
PAs Producer
  • Usage
    212
  • Modification rate
    100%
  • Avg file size
    81 KB

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.

Name fingerprints

Also goes by

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

ActiveReports Developer77.2%
ActiveReports 1322.8%

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.

Most common
ActiveReports Developer
77.2% of appearances
Variant spread
2 distinct strings
Long-tail share: 22.8%
Observed range
17 Apr 2026 → 22 Apr 2026

Distributions

What ships alongside ActiveReports

The PDF versions ActiveReports 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 ActiveReports is the Producer).

PDF 1.3100.0%

Related profiles

Tools you’ll see next to ActiveReports

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

P23% co-occurrence
macOS Print to PDF
Appearances731
Mod rate65%

Long tail

Notable observations

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

Pages parsed
1,397
Oldest observed
17 Apr 2026 — 21 days 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 →