@turf/length
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): tslib and @types/geojson are standard TypeScript build dependencies, not suspicious third-party packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Turf.js contributors; part of org-level maintainer update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of deniscarriere is consistent with Turf.js org maintainer rotation, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the v6→v7 development cycle; consistent with other @turf/* packages in this batch. | ai | |
| provenance | publisher-changed | AI (provenance): mdfedderly is the Turf.js org publisher for the v7 monorepo release; consistent across all @turf/* packages. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson is a type-only dep loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit dep pattern stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Turf.js package; provenance absence is consistent across the entire @turf/* namespace. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 5 / 9 | |
| 7.3.4 | 5 / 9 | |
| 7.3.3 | 5 / 9 | |
| 7.3.2 | 5 / 9 | |
| 7.3.1 | 5 / 9 | |
| 7.3.0 | 5 / 10 | |
| 6.5.0 | 3 / 9 |
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.