@turf/boolean-equal
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 | new-deps-added | AI (publish-pattern): geojson-equality-ts is a TS-compatible replacement for geojson-equality; tslib/@types/geojson are standard TS build deps. | ai | |
| provenance | publisher-changed | AI (provenance): mdfedderly is the established Turf.js monorepo publisher with 13 approved packages; transition is consistent across the org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Turf.js contributors; org-wide team transition, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of deniscarriere consistent with Turf.js org-wide maintainer rotation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version cycle; v7 monorepo release pattern across all @turf/* packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime helper; not directly imported by convention. | 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 used transitively; phantom-dep heuristic unreliable for monorepo peers. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 6 / 9 | |
| 7.3.4 | 6 / 10 | |
| 7.3.3 | 6 / 10 | |
| 7.3.2 | 6 / 10 | |
| 7.3.1 | 6 / 10 | |
| 7.3.0 | 6 / 11 | |
| 6.5.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
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.
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.
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.
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.