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

Aspose

Aspose 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 870 appearances across the HTPBE? corpus.

Modification rate
39%-9pp below baseline
Corpus baseline: 48%
Total appearances
870
4.2% of corpus
Modification rate
39%
-9pp below baseline
Role split
58%C/42%P
Creator vs Producer share of appearances

Corpus profile

How Aspose shows up in HTPBE? corpus

Aspose is a commercial component suite (Aspose.PDF, Aspose.Words) used both for legitimate server-side document generation in enterprise apps and for programmatic editing/conversion of existing PDFs.

Aspose appears across both legitimate first-generation output and re-save flows. Signal: when Aspose is the latest Producer on a document whose Creator was an institutional source, that producer/creator mismatch is one of the markers we surface — together with any incremental-update or signature-removal evidence on the file.

The signal
Aspose appears across both legitimate first-generation output and re-save flows.

Role in the workflow

How Aspose 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 · 58%
As Producer · 42%P
CAs Creator
  • Usage
    503
  • Modification rate
    48%
  • Avg file size
    707 KB
PAs Producer
  • Usage
    367
  • Modification rate
    26%
  • Avg file size
    897 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 Aspose in the wild. All are merged into the same canonical profile.

Aspose Pty Ltd.41.5%
Aspose.PDF for .NET 22.12.028.6%
Aspose Ltd.16.3%
Aspose.PDF for .NET 21.9.07.7%
Aspose.PDF for .NET 25.6.01.3%
Aspose.Pdf 8.3.11.0%
Aspose.PDF for .NET 23.5.00.7%
Aspose.Words for .NET 16.4.0.00.6%
Aspose.Words for Java 14.9.0.00.3%
Aspose.Words for Java 18.120.3%
Aspose.Words for Java 20.11.00.3%
Aspose.Pdf for .NET 9.8.00.2%
Aspose.Pdf for .NET 17.4.00.2%
Aspose.Words for .NET 19.80.1%
Aspose.Words for .NET 15.10.0.00.1%
Aspose.PDF for .NET 24.10.00.1%
Aspose.PDF for .NET 24.6.00.1%
Aspose.Words for .NET 23.9.00.1%
Aspose.PDF for .NET 19.100.1%
Aspose.PDF for .NET 25.9.00.1%

Why variants matter

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

Most common
Aspose Pty Ltd.
41.5% of appearances
Variant spread
20 distinct strings
Long-tail share: 58.5%
Observed range
9 Dec 2015 → 15 May 2026

Distributions

What ships alongside Aspose

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

PDF versions written

Most output is PDF 1.7 (96% of files where Aspose is the Producer).

PDF 1.796.0%
PDF 1.42.0%
PDF 1.51.1%
PDF 1.60.9%

Common Producers when Aspose is the Creator

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

iText18.7%
macOS Print to PDF13.7%

Common Creators when Aspose is the Producer

Aspose sits upstream in 95% of cases — read this row as “what kinds of documents end up routed through Aspose.”

Aspose94.7%
Microsoft Word4.7%
Jan Piet Vermaas0.6%

Related profiles

Tools you’ll see next to Aspose

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

P11% co-occurrence
iText
Appearances1,717
Mod rate46%
P8% co-occurrence
macOS Print to PDF
Appearances747
Mod rate64%
C2% co-occurrence
Microsoft Word
Appearances2,124
Mod rate81%
C0% co-occurrence
Jan Piet Vermaas
Appearances2
Mod rate100%

Long tail

Notable observations

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

Pages parsed
2,205
Oldest observed
9 Dec 2015 — over 10 years 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 →