← Home

@terascope/geo-utils

A collection of Teraslice Geo Utilities

10
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

terascope-cigodberjsnoble1

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 10 of 10)

Version Deps Published
2.7.0 16 / 1
2.6.0 16 / 1
2.4.1 16 / 1
2.3.3 16 / 1
2.2.1 16 / 1
2.0.8 16 / 1
2.0.6 16 / 1
2.0.4 16 / 1
2.0.3 16 / 1
2.0.0 16 / 1

v2.7.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.6.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.