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

jsPDF

jsPDF 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
39%-10pp below baseline
Corpus baseline: 49%
Corpus share
0.29%
Share of all analyzed appearances
Modification rate
39%
-10pp below baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How jsPDF shows up in HTPBE? corpus

jsPDF is a client-side JavaScript library that builds PDFs in the browser. Common in client-rendered receipt and certificate generators.

jsPDF appears on receipts, certificates and other documents built in the browser. Context matters more than the name – HTPBE? examines the whole file.

The signal
jsPDF appears on receipts, certificates and other documents built in the browser.

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 jsPDF 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

  • The figures cover 80 files. Larger than a handful, but still a sample of what was submitted, not of all PDFs in the world.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of jsPDF.
  • 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 jsPDF 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 · 0%
As Producer · 100%P
CAs creator
  • Share of appearances
    0%
  • Modification rate
    0%
PAs producer
  • Share of appearances
    100%
  • Modification rate
    39%
  • Avg file size
    1.3 MB

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 jsPDF in the wild. All are merged into the same canonical profile.

jsPDF 4.2.031.3%
jsPDF 3.0.326.3%
jsPDF 2.5.211.3%
jsPDF 4.2.110.0%
jsPDF 2.5.15.0%
jsPDF 1.5.35.0%
jsPDF 3.0.13.8%
jsPDF 3.0.43.8%
jsPDF 4.0.02.5%
jsPDF 3.0.21.3%

Why variants matter

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

Most common
jsPDF 4.2.0
31.3% of appearances
Variant spread
10 distinct strings
Long-tail share: 68.8%
Observed range
17.08.2023 → 20.11.2026

Distributions

What ships alongside jsPDF

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

PDF versions written

Most output is PDF 1.3 (89% of files where jsPDF is the Producer).

PDF 1.389.5%
PDF 1.710.5%

Common Creators when jsPDF is the Producer

Bank of America sits upstream in 32% of cases — read this row as “what kinds of documents end up routed through jsPDF.”

Bank of America32.1%
PNC BANK21.4%
BANK OF AMERICA21.4%
US BANK10.7%
PDF-Vault10.7%
Apache FOP3.6%

Related profiles

Tools you’ll see next to jsPDF

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

C11% co-occurrence
Bank of America
Corpus share0.40%
Mod rate63%
C8% co-occurrence
PNC BANK
Corpus share0.02%
Mod rate67%
C8% co-occurrence
BANK OF AMERICA
Corpus share0.02%
Mod rate83%
C4% co-occurrence
US BANK
Corpus share0.01%
Mod rate100%
C4% co-occurrence
PDF-Vault
Corpus share0.01%
Mod rate0%

Long tail

Notable observations

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

Digitally signed
4%

Of files carry at least one digital signature

Avg pages per document
2.0
Oldest observed
17.08.2023 — over 3 years ago

FAQ

jsPDF in PDF metadata: common questions

What is jsPDF?

jsPDF is a client-side JavaScript library that builds PDFs in the browser. Common in client-rendered receipt and certificate generators.

Why does jsPDF 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 jsPDF 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 jsPDF in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many jsPDF 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 jsPDF statistics?

The figures describe the 80 files in the HTPBE? corpus that list jsPDF 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 jsPDF and not a prediction for any single document.

Can I compare jsPDF 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 jsPDF?

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 →