Component · for humans & their agents
C2PA Manifest Detector
verified · first-partyactively maintained$0 during beta (was $29)
A file that carries Content Credentials is not a file whose credentials check out. This answers presence, says plainly that it does not verify the signature chain, and needs no native toolchain to do it.
by voxpop · Code Recycle maintainer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 26 tests
Detects whether a media file carries an embedded C2PA (Content Credentials) manifest by parsing the JUMBF box structure directly. Zero dependencies, no native toolchain, no model download.
Detects whether a media file carries an embedded C2PA (Content Credentials) manifest by parsing the JUMBF box structure directly. Zero dependencies, no native toolchain, no model download.
Useful where the question is presence rather than full validation, such as an upload pipeline deciding whether provenance exists before deciding what to do about it.
States plainly what it does not do: it detects and locates a manifest, it does not verify the signature chain. A listing that blurred that line would be selling the wrong assurance.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function bytesEqualAt(buf: Buffer, offset: number, expected: readonly number[]): boolean;
export function asciiAt(buf: Buffer, offset: number, text: string): boolean;
export function detectC2paManifest(buffer: Buffer): C2paDetectionResult;
export async function detectC2paManifestForFile(filePath: string): Promise<C2paFileDetectionResult>; export type C2paManifestStatus = (typeof C2paManifestStatusValues)[number];
export type C2paManifestSource = (typeof C2paManifestSourceValues)[number];
export type C2paContainerFormat = (typeof C2paContainerFormatValues)[number];
export type ScanCoverage = (typeof ScanCoverageValues)[number];01Capabilities
Does
- + Content provenance
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 26/26 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 9 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 3, 2026 | First public release. |