StreamServe 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
StreamServe is one of the PDF-handling tools surfaced in the HTPBE? corpus. StreamServe appears predominantly as the Producer (100% of its occurrences) — i.e. on documents whose original Creator was a different application and that subsequently passed through StreamServe on the way out.
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when StreamServe 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 StreamServe acts as Creator, 0% carry modification markers; on documents where it acts as Producer, 50% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against StreamServe or its users.
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 StreamServe in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 4 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions StreamServe writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.6 (50% of files where StreamServe is the Producer).
Related profiles
Other tools that frequently share metadata with StreamServe in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the StreamServe corpus — useful context, but treat each row as a single data point rather than a strong signal.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.