@pnpm/get-context
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established pnpm monorepo package; lack of provenance is consistent across all its versions and not a risk indicator here. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1001.2.11 | 10 / 3 | |
| 1001.2.10 | 10 / 3 | |
| 1001.2.9 | 10 / 3 | |
| 1001.2.8 | 10 / 3 | |
| 1001.2.7 | 10 / 3 | |
| 1001.2.6 | 10 / 3 | |
| 1001.2.4 | 10 / 3 | |
| 1001.2.3 | 10 / 3 | |
| 1001.2.2 | 10 / 3 | |
| 1001.2.1 | 10 / 3 | |
| 1001.2.0 | 10 / 3 | |
| 1001.1.14 | 9 / 3 | |
| 1001.1.13 | 9 / 3 | |
| 1001.1.12 | 9 / 3 | |
| 1001.1.11 | 9 / 3 | |
| 1001.1.10 | 9 / 3 | |
| 1001.1.9 | 9 / 3 | |
| 1001.1.8 | 9 / 3 | |
| 1001.1.6 | 9 / 3 | |
| 1001.1.5 | 9 / 3 | |
| 1001.1.4 | 9 / 3 | |
| 1001.1.3 | 9 / 3 | |
| 1001.1.2 | 9 / 3 | |
| 1001.1.1 | 9 / 3 | |
| 1001.1.0 | 9 / 3 | |
| 1001.0.14 | 10 / 3 | |
| 1001.0.13 | 10 / 3 | |
| 1001.0.12 | 10 / 3 | |
| 1001.0.11 | 10 / 3 | |
| 1001.0.10 | 10 / 3 | |
| 1001.0.9 | 10 / 3 | |
| 1001.0.8 | 10 / 3 | |
| 1001.0.7 | 10 / 3 | |
| 1001.0.6 | 10 / 3 | |
| 1001.0.5 | 10 / 3 | |
| 1001.0.4 | 10 / 3 | |
| 1001.0.3 | 10 / 3 | |
| 1001.0.2 | 10 / 3 | |
| 1001.0.1 | 10 / 3 | |
| 1001.0.0 | 10 / 3 |
v1001.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1001.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zkochan) than the most recent previously approved version (pnpmuser) on 2024-12-18, but zkochan 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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.