pino-http-print
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
matteo.collinajsumnerswatsondavidmarkclements
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jsumners is a long-standing pinojs org contributor with 462 approved packages; transition from matteo.collina is a legitimate maintainer handoff within the same GitHub org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): sonic-boom is a core pino ecosystem package published by the pinojs org; not a suspicious dependency for a pino-adjacent tool. | ai | |
| provenance | no-provenance | AI (provenance): Established pinojs ecosystem package from a highly trusted publisher; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
v4.0.0
2 findings
HIGH
Publisher changed: matteo.collina → jsumners (on 2025-11-05)
provenance
This version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.