@turf/bbox-clip
Takes a Feature and a bbox and clips the feature to the bbox using lineclip.
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): Turf monorepo publishes via GitHub Actions CI with SLSA attestation; this is the expected publisher going forward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA attestation confirms legitimate CI publish. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson is a type-only dependency loaded by convention; stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 4 / 10 | |
| 7.3.4 | 4 / 10 | |
| 7.3.3 | 4 / 10 | |
| 7.3.2 | 4 / 10 | |
| 7.3.1 | 4 / 10 | |
| 7.3.0 | 4 / 11 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.