proj4
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:curl | AI (npm-metadata): Dev-only test dependency via git URL, no runtime impact; stable for this old package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; absence of Sigstore attestation is common and not a risk indicator here. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI/CD with Sigstore attestation; strong supply chain integrity signal. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 2.21.0 | 2 / 14 | |
| 2.20.9 | 2 / 14 | |
| 2.20.8 | 2 / 14 | |
| 2.20.7 | 2 / 14 | |
| 2.20.6 | 2 / 16 | |
| 2.20.5 | 2 / 16 | |
| 2.20.4 | 2 / 16 | |
| 2.20.3 | 2 / 16 | |
| 2.20.2 | 2 / 16 | |
| 2.20.1 | 2 / 16 | |
| 2.20.0 | 2 / 16 | |
| 2.19.10 | 2 / 16 | |
| 2.19.9 | 2 / 16 | |
| 2.19.8 | 2 / 17 | |
| 2.19.7 | 2 / 17 | |
| 2.19.6 | 2 / 17 | |
| 2.19.5 | 2 / 17 | |
| 2.19.4 | 2 / 17 | |
| 2.19.3 | 2 / 16 | |
| 2.19.2 | 2 / 15 | |
| 2.19.1 | 2 / 16 | |
| 2.19.0 | 2 / 16 | |
| 2.17.0 | 3 / 15 | |
| 2.16.2 | 3 / 14 | |
| 2.16.1 | 3 / 14 | |
| 2.15.0 | 2 / 16 | |
| 2.14.0 | 2 / 16 | |
| 2.13.2 | 2 / 16 | |
| 2.13.1 | 2 / 16 | |
| 2.13.0 | 2 / 16 | |
| 2.12.1 | 2 / 16 | |
| 2.12.0 | 2 / 16 | |
| 2.6.3 | 2 / 16 | |
| 2.6.2 | 2 / 16 | |
| 2.6.1 | 2 / 16 | |
| 2.6.0 | 2 / 16 | |
| 2.5.0 | 2 / 15 | |
| 2.4.4 | 2 / 15 | |
| 2.4.3 | 2 / 15 | |
| 2.4.1 | 2 / 15 | |
| 2.4.0 | 2 / 15 | |
| 2.3.17 | 1 / 13 | |
| 2.3.16 | 1 / 13 | |
| 2.3.15 | 1 / 13 | |
| 2.3.14 | 1 / 13 | |
| 2.3.13 | 1 / 13 | |
| 2.3.12 | 1 / 13 | |
| 2.3.11 | 1 / 13 | |
| 2.3.10 | 1 / 13 | |
| 2.3.9 | 1 / 13 | |
| 2.3.8 | 1 / 13 |
v2.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.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.
v2.12.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.
v2.6.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.
v2.6.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.
v2.6.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.
v2.6.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.
v2.5.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.
v2.4.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.
v2.4.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.
v2.4.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.
v2.4.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.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.