← Home

@pnpm/core-loggers

Core loggers of pnpm

16
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

pnpmuserzkochan

Keywords

pnpmpnpm11

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): pnpmuser is the established pnpm publishing account (100 approved, 0 rejected, 1434 days history). SLSA provenance attestation confirms CI/CD build integrity. Publisher change reflects pnpm's publishing workflow evolution. ai
publish-pattern dormant-publish AI (publish-pattern): pnpm uses major version number series tied to pnpm releases; gaps between series appear as dormancy but reflect intentional versioning, not account inactivity. ai

Versions (showing 16 of 16)

Version Deps Published
1100.2.1 1 / 2
1100.2.0 1 / 2
1100.1.4 1 / 2
1100.1.3 1 / 2
1100.1.2 1 / 2
1100.1.1 1 / 2
1100.1.0 1 / 2
1100.0.2 1 / 2
1100.0.1 1 / 2
1100.0.0 1 / 2
1001.0.10 1 / 2
1001.0.9 1 / 2
1001.0.8 1 / 2
1001.0.7 1 / 2
1001.0.6 1 / 2
1001.0.5 1 / 2

v1100.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1100.2.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: pnpmuser → GitHub Actions (on 2026-06-11) provenance

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

v1100.1.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1100.1.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1100.1.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1100.1.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1100.1.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: pnpmuser → GitHub Actions (on 2026-05-18) provenance

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

v1100.0.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: pnpmuser → GitHub Actions (on 2026-05-11) provenance

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

v1001.0.10

2 findings
HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

INFO Publisher changed: GitHub Actions → pnpmuser (on 2026-06-10, known maintainer) provenance

This version was published by a different npm account (pnpmuser) than the most recent previously approved version (GitHub Actions) on 2026-06-10, but pnpmuser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1001.0.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1001.0.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1001.0.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1001.0.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.