@turf/boolean-contains
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with monorepo release cadence; SLSA provenance confirms legitimate publish. | ai | |
| provenance | publisher-changed | AI (provenance): Turf monorepo migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI origin. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known Turf.js maintainers added as part of monorepo governance transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation in established Turf.js project; not indicative of takeover. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit import pattern is expected. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@turf/helpers | AI (phantom-deps): Same-org package; likely re-exported or used transitively within the monorepo build. | ai | |
| provenance | no-provenance | AI (provenance): Turf.js predates Sigstore provenance; absence is expected for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 8 / 10 | |
| 7.3.4 | 8 / 11 | |
| 7.3.3 | 8 / 11 | |
| 7.3.2 | 8 / 11 | |
| 7.3.1 | 7 / 11 | |
| 7.3.0 | 7 / 12 | |
| 6.5.0 | 5 / 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
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.