← Home

@turf/distance

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rowanwinstmcwmorganherlockertcqlmdfedderlytwelchjamesmilnerukmorgan.herlockersmallsaucepan

Keywords

turfdistancemileskm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Turf.js project has multiple maintainers; additions reflect legitimate project governance. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer rotation in a large open-source project; no malicious indicators. ai
publish-pattern new-deps-added AI (publish-pattern): tslib and @types/geojson are standard TypeScript ecosystem deps, not suspicious additions. 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
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): @types/geojson is a type-only package loaded by convention in TS projects; not directly imported. ai
provenance no-provenance AI (provenance): Established Turf.js monorepo package; lack of provenance is consistent across all versions and not a risk signal here. ai

Versions (showing 4 of 4)

Version Deps Published
7.3.5 4 / 9
7.3.2 4 / 9
7.3.1 4 / 9
6.5.0 2 / 9

v7.3.5

1 finding
INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: rowanwins → mdfedderly (on 2026-01-14) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.3.1

2 findings
HIGH Publisher changed: rowanwins → mdfedderly (on 2025-11-27) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.