@turf/isobands
Takes a grid of values (GeoJSON format) and a set of threshold ranges. It outputs polygons that group areas within those ranges, effectively creating filled contour isobands.
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 | publisher-changed | AI (provenance): Transition from maintainer to GitHub Actions CI/CD; SLSA provenance confirms automated publish. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo release cadence; dormancy reflects normal Turf release cycle. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep used by TypeScript compilation. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only dependency; not directly imported at runtime. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 9 / 14 | |
| 7.3.4 | 9 / 14 | |
| 7.3.3 | 9 / 14 | |
| 7.3.2 | 9 / 14 | |
| 7.3.1 | 9 / 14 | |
| 7.3.0 | 9 / 15 |
v7.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.