@pnpm/default-resolver — Greenflagged

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

pnpmuserzkochan

Keywords

pnpmpnpm10npmresolver

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): pnpm monorepo migrated to GitHub Actions publishing with SLSA provenance attestation; the publisher change is legitimate and expected to persist across future versions.	ai	2026/04/27
dependencies	unvetted-dep:@pnpm/npm-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/node.resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/fetching-types	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/git-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/tarball-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/resolving.bun-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/resolving.deno-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@pnpm/local-resolver	AI (dependencies): Internal pnpm monorepo sibling package; published from the same repo with SLSA provenance. Unvetted status reflects review queue lag, not a security concern.	ai	2026/04/25

Versions (showing 40 of 40)

Version	Deps	Published
1002.3.10	10 / 2	2026-05-27
1002.3.9	10 / 2	2026-05-06
1002.3.8	10 / 2	2026-03-24
1002.3.7	10 / 2	2026-03-11
1002.3.6	10 / 2	2026-03-07
1002.3.5	10 / 2	2026-02-23
1002.3.4	10 / 2	2026-02-17
1002.3.3	10 / 2	2026-02-09
1002.3.2	10 / 2	2026-02-07
1002.3.1	10 / 2	2026-01-26
1002.3.0	10 / 2	2026-01-19
1002.2.23	10 / 2	2026-01-09
1002.2.22	10 / 2	2025-12-30
1002.2.21	10 / 2	2025-12-23
1002.2.20	10 / 2	2025-12-19
1002.2.19	10 / 2	2025-12-15
1002.2.18	10 / 2	2025-12-08
1002.2.17	10 / 2	2025-12-02
1002.2.16	10 / 2	2025-11-27
1002.2.15	10 / 2	2025-11-20
1002.2.14	10 / 2	2025-11-12
1002.2.13	10 / 2	2025-11-09
1002.2.12	10 / 2	2025-10-28
1002.2.11	10 / 2	2025-10-21
1002.2.10	10 / 2	2025-10-14
1002.2.9	10 / 2	2025-10-09
1002.2.8	10 / 2	2025-09-29
1002.2.7	10 / 2	2025-09-22
1002.2.6	10 / 2	2025-09-17
1002.2.5	10 / 2	2025-09-13
1002.2.4	10 / 2	2025-09-12
1002.2.3	10 / 2	2025-09-01
1002.2.2	10 / 2	2025-08-19
1002.2.1	10 / 2	2025-08-07
1002.2.0	10 / 2	2025-07-31
1002.1.2	8 / 2	2025-07-23
1002.1.1	7 / 2	2025-07-09
1002.1.0	7 / 2	2025-06-08
1002.0.2	7 / 2	2025-06-02
1002.0.1	7 / 2	2025-05-13

v1002.3.10

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.

v1002.3.9

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.

v1002.3.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.

v1002.3.7

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-03-11) provenance

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

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.

v1002.3.6

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-03-07) provenance

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

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.

v1002.3.5

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-02-23) provenance

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

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.

v1002.3.4

2 findings

HIGH Publisher changed: pnpmuser → zkochan (on 2026-02-17) provenance

This version was published by a different npm account than previous versions on 2026-02-17. 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.

v1002.3.3

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-02-09) provenance

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

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.

v1002.3.2

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-02-07) provenance

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

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.

v1002.3.1

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-01-26) provenance

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

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.

v1002.3.0

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-01-19) provenance

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

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.

v1002.2.23

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2026-01-09) provenance

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

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.

v1002.2.22

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-12-30) provenance

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

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.

v1002.2.21

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-12-23) provenance

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

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.

v1002.2.20

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-12-19) provenance

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

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.

v1002.2.19

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-12-15) provenance

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

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.

v1002.2.18

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-12-08) provenance

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

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.

v1002.2.17

2 findings

HIGH Publisher changed: pnpmuser → zkochan (on 2025-12-02) provenance

This version was published by a different npm account than previous versions on 2025-12-02. 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.

v1002.2.16

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-11-27) provenance

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

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.

v1002.2.15

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-11-20) provenance

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

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.

v1002.2.14

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-11-12) provenance

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

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.

v1002.2.13

2 findings

HIGH Publisher changed: pnpmuser → GitHub Actions (on 2025-11-09) provenance

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

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.

v1002.2.12

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.

v1002.2.11

1 finding

LOW No provenance attestation provenance

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

v1002.2.10

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: zkochan → pnpmuser (on 2025-10-14) provenance

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

v1002.2.9

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: zkochan → pnpmuser (on 2025-10-09) provenance

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

v1002.2.8

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: pnpmuser → zkochan (on 2025-09-29) provenance

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

v1002.2.7

1 finding

LOW No provenance attestation provenance

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

v1002.2.6

1 finding

LOW No provenance attestation provenance

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

v1002.2.5

1 finding

LOW No provenance attestation provenance

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

v1002.2.4

1 finding

LOW No provenance attestation provenance

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

v1002.2.3

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: zkochan → pnpmuser (on 2025-09-01) provenance

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

v1002.2.2

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: zkochan → pnpmuser (on 2025-08-19) provenance

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

v1002.2.1

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: pnpmuser → zkochan (on 2025-08-07) provenance

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

v1002.2.0

1 finding

LOW No provenance attestation provenance

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

v1002.1.2

1 finding

LOW No provenance attestation provenance

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

v1002.1.1

1 finding

LOW No provenance attestation provenance

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

v1002.1.0

1 finding

LOW No provenance attestation provenance

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

v1002.0.2

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.

v1002.0.1

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.