@pnpm/store-connection-manager
Create a direct pnpm store controller or connect to a running store server
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): zkochan is Zoltan Kochan, the original pnpm creator. The switch from pnpmuser (CI bot) to zkochan (human maintainer) is a legitimate and expected transition for this core pnpm package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of the pnpmuser→zkochan account transition, not a true gap in maintenance. pnpm is an actively maintained project with 448 versions in registry. | ai | |
| provenance | no-provenance | AI (provenance): Official pnpm monorepo package published by pnpmuser with 41 approved packages; lack of provenance is consistent across all pnpm packages and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:dir-is-case-sensitive | AI (phantom-deps): dir-is-case-sensitive is a declared runtime dependency used in config; phantom-dep finding is a false positive for this package's usage pattern. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1002.3.21 | 10 / 2 | |
| 1002.3.20 | 10 / 2 | |
| 1002.3.19 | 10 / 2 | |
| 1002.3.18 | 10 / 2 | |
| 1002.3.17 | 10 / 2 | |
| 1002.3.16 | 10 / 2 | |
| 1002.3.15 | 10 / 2 | |
| 1002.3.14 | 10 / 2 | |
| 1002.3.13 | 10 / 2 | |
| 1002.3.12 | 10 / 2 | |
| 1002.3.11 | 10 / 2 | |
| 1002.3.10 | 10 / 2 | |
| 1002.3.9 | 10 / 2 | |
| 1002.3.8 | 10 / 2 | |
| 1002.3.7 | 10 / 2 | |
| 1002.3.6 | 10 / 2 | |
| 1002.3.5 | 10 / 2 | |
| 1002.3.4 | 10 / 2 | |
| 1002.3.3 | 10 / 2 | |
| 1002.3.2 | 10 / 2 | |
| 1002.3.1 | 10 / 2 | |
| 1002.3.0 | 10 / 2 | |
| 1002.2.4 | 10 / 2 | |
| 1002.2.3 | 10 / 2 | |
| 1002.2.2 | 10 / 2 | |
| 1002.2.1 | 10 / 2 | |
| 1002.2.0 | 10 / 2 | |
| 1002.1.3 | 10 / 2 | |
| 1002.1.2 | 10 / 2 | |
| 1002.1.1 | 10 / 2 | |
| 1002.1.0 | 10 / 2 | |
| 1002.0.11 | 10 / 2 | |
| 1002.0.10 | 10 / 2 | |
| 1002.0.9 | 10 / 2 | |
| 1002.0.8 | 10 / 2 | |
| 1002.0.7 | 10 / 2 | |
| 1002.0.6 | 10 / 2 | |
| 1002.0.5 | 10 / 2 | |
| 1002.0.4 | 10 / 2 | |
| 1002.0.3 | 10 / 2 | |
| 1002.0.2 | 10 / 2 | |
| 1002.0.1 | 10 / 2 |
v1002.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.3.15
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.4
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.2
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.