@turf/circle
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): mdfedderly is an established Turf.js maintainer with 13 approved packages; org-level transition, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are part of the legitimate Turf.js v7 team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainer consistent with planned Turf.js project handoff. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tslib and @types/geojson are standard TypeScript runtime/type deps added as part of v7 TypeScript migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the Turf v7 major release cycle, not a takeover; consistent with coordinated monorepo upgrade. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson is a type-only dependency; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit usage is expected in compiled TS packages. | ai | |
| dependencies | unvetted-dep:@turf/destination | AI (dependencies): Sibling Turf.js monorepo package; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.3.5 | 4 / 11 | |
| 7.3.4 | 4 / 11 | |
| 7.3.3 | 4 / 11 | |
| 7.3.2 | 4 / 11 | |
| 7.3.1 | 4 / 11 | |
| 7.3.0 | 4 / 12 | |
| 6.5.0 | 2 / 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.