jsPDF 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 statisticsForensic verdictBased on this tool’s share of the HTPBE? corpus.
Corpus profile
jsPDF is a client-side JavaScript library that builds PDFs in the browser. Common in client-rendered receipt and certificate generators.
jsPDF as the latest Producer on a document whose Creator was institutional indicates client-side reconstruction — that producer/creator mismatch is the contextual signal.
Role in the workflow
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.
Name fingerprints
Different version strings and spellings observed for jsPDF in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 9 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions jsPDF writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.3 (88% of files where jsPDF is the Producer).
Bank of America sits upstream in 38% of cases — read this row as “what kinds of documents end up routed through jsPDF.”
Related profiles
Other tools that frequently share metadata with jsPDF in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the jsPDF corpus – useful context, but treat each row as a single data point rather than a strong signal.
Of files carry at least one digital signature
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.