@terascope/geo-utils
A collection of Teraslice Geo Utilities
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package. | ai | |
| dependencies | unvetted-dep:geo-tz | AI (dependencies): geo-tz is a well-known timezone lookup library; stable legitimate dependency for a geo-utils package. | ai | |
| dependencies | unvetted-dep:latlon-geohash | AI (dependencies): latlon-geohash is a well-known geohash library; stable legitimate dependency for a geo-utils package. | ai | |
| phantom-deps | phantom-dep:@turf/bbox | AI (phantom-deps): @turf/bbox is explicitly declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Terascope org package; thin README/no keywords are cosmetic, not spam indicators. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 16 / 2 | |
| 2.14.0 | 16 / 2 | |
| 2.13.0 | 16 / 2 | |
| 2.12.1 | 16 / 2 | |
| 2.12.0 | 16 / 2 | |
| 2.11.1 | 16 / 2 | |
| 2.11.0 | 16 / 2 | |
| 2.10.1 | 16 / 2 | |
| 2.10.0 | 16 / 1 | |
| 2.9.1 | 16 / 1 | |
| 2.9.0 | 16 / 1 | |
| 2.8.1 | 16 / 1 | |
| 2.8.0 | 16 / 1 | |
| 2.7.0 | 16 / 1 | |
| 2.6.0 | 16 / 1 | |
| 2.5.3 | 16 / 1 | |
| 2.5.2 | 16 / 1 | |
| 2.5.1 | 16 / 1 | |
| 2.5.0 | 16 / 1 | |
| 2.4.2 | 16 / 1 | |
| 2.4.1 | 16 / 1 | |
| 2.4.0 | 16 / 1 | |
| 2.3.3 | 16 / 1 | |
| 2.3.2 | 16 / 1 | |
| 2.3.1 | 16 / 1 | |
| 2.3.0 | 16 / 1 | |
| 2.2.2 | 16 / 1 | |
| 2.2.1 | 16 / 1 | |
| 2.2.0 | 16 / 1 | |
| 2.1.0 | 16 / 1 | |
| 2.0.8 | 16 / 1 | |
| 2.0.7 | 16 / 1 | |
| 2.0.6 | 16 / 1 | |
| 2.0.5 | 16 / 1 | |
| 2.0.4 | 16 / 1 | |
| 2.0.3 | 16 / 1 | |
| 2.0.2 | 16 / 1 | |
| 2.0.1 | 16 / 1 | |
| 2.0.0 | 16 / 1 |
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.2
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (terascope-ci) on 2026-03-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
v2.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
v2.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.