← Home

@contentauth/c2pa-node

2
Versions
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

emenschandyp-adobecaiopensrc

Keywords

c2pa

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Native Rust binding; postinstall downloads prebuilt binaries — documented pattern for this package. ai
publish-pattern new-deps-added AI (publish-pattern): All new deps (node-fetch, unzipper, cli-progress, etc.) support the prebuilt binary download workflow; consistent with package purpose. ai
source-diff large-new-source-files AI (source-diff): Major version jump adding full Rust binding infrastructure; size increase is expected. ai
source-diff source-size-tripled AI (source-diff): Growth from 2KB to 140KB reflects addition of Cargo.lock and binding source files, not injected payloads. ai

Versions (showing 2 of 2)

Version Deps Published
0.5.5 9 / 24
0.1.0 1 / 20

v0.5.5

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.cjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.