@developmentseed/proj
Utilities for geographic reprojections.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA Sigstore attestation provides stronger integrity guarantee; missing gitHead is a minor metadata gap, not a supply-chain risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 1 / 4 | |
| 0.6.1 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 0 / 3 | |
| 0.3.0 | 0 / 3 |
v0.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.