← Home

pino-pretty

Prettifier for Pino log lines

51
Versions
MIT
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.collinajsumnerswatson

Keywords

pino

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jsumners (James Sumners) is the listed author and a known pinojs org maintainer; this is a legitimate maintainer transition, not a compromise. ai

Versions (showing 51 of 93)

View all versions
Version Deps Published
13.1.3 13 / 14
13.1.2 13 / 14
13.1.1 13 / 15
13.1.0 13 / 15
13.0.0 13 / 12
12.1.0 14 / 12
12.0.0 14 / 12
11.3.0 14 / 12
11.2.2 14 / 12
11.2.1 14 / 11
11.2.0 14 / 11
11.1.0 14 / 11
11.0.0 14 / 10
10.3.1 14 / 10
10.3.0 14 / 10
10.2.3 14 / 10
10.2.2 14 / 10
10.2.1 14 / 10
10.2.0 14 / 9
10.1.0 14 / 9
10.0.1 14 / 9
10.0.0 14 / 9
9.4.1 14 / 9
9.4.0 14 / 9
9.3.0 14 / 9
9.2.0 14 / 9
9.1.1 14 / 9
9.1.0 14 / 9
9.0.1 14 / 9
9.0.0 14 / 9
8.1.0 14 / 9
8.0.0 13 / 9
7.6.1 13 / 9
7.6.0 13 / 9
7.5.4 13 / 9
7.5.3 12 / 9
7.5.2 12 / 9
7.5.1 12 / 9
7.5.0 12 / 9
7.4.0 12 / 9
7.3.0 12 / 9
7.2.0 12 / 9
7.1.0 12 / 9
7.0.1 12 / 9
7.0.0 12 / 9
6.0.0 12 / 9
5.1.3 12 / 9
5.1.2 12 / 9
5.1.1 12 / 9
5.1.0 13 / 8
5.0.2 13 / 8

v13.1.3

1 finding
LOW No provenance attestation provenance

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

v13.1.2

2 findings
HIGH Publisher changed: matteo.collina → jsumners (on 2025-10-10) provenance

This version was published by a different npm account than previous versions on 2025-10-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v13.1.1

2 findings
HIGH Publisher changed: matteo.collina → jsumners (on 2025-07-30) provenance

This version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v13.1.0

1 finding
LOW No provenance attestation provenance

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

v13.0.0

1 finding
LOW No provenance attestation provenance

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

v12.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jsumners → matteo.collina (on 2024-11-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-11-08. This could indicate a legitimate maintainer transition or an account compromise.

v12.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: matteo.collina → jsumners (on 2024-11-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-11-07. This could indicate a legitimate maintainer transition or an account compromise.

v11.3.0

1 finding
LOW No provenance attestation provenance

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

v11.2.2

1 finding
LOW No provenance attestation provenance

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

v11.2.1

1 finding
LOW No provenance attestation provenance

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

v11.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: matteo.collina → jsumners (on 2024-06-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-06-09. This could indicate a legitimate maintainer transition or an account compromise.

v11.1.0

1 finding
LOW No provenance attestation provenance

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