@squawk/geo
Geospatial utilities: great-circle distance, bearing, midpoint, destination point, and polygon containment
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): @squawk/geo is a scoped geospatial package; 'geo' is a legitimate abbreviation with no brand impersonation of 'glob'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @squawk/geo is a scoped geospatial package; 'geo' is a legitimate abbreviation with no brand impersonation of 'got'. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 3 / 1 | |
| 0.4.2 | 3 / 1 | |
| 0.4.1 | 3 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.3 | 2 / 1 | |
| 0.3.2 | 2 / 1 | |
| 0.3.1 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.1 | 2 / 1 | |
| 0.2.0 | 2 / 1 |
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.