← Home

@turf/buffer

npm Repository Homepage
6
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

bufferoffsetpolygonlinestringpointgeojsonturf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD is a security improvement, confirmed by SLSA provenance attestation. Consistent with Turfjs monorepo migration to automated publishing. ai
phantom-deps phantom-dep:@turf/bbox AI (phantom-deps): Same-org sibling package in the Turfjs monorepo; phantom import pattern is stable across versions of this package. ai
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): Type-only package loaded by convention in TypeScript GeoJSON packages; not a security concern. ai
phantom-deps phantom-dep:@turf/projection AI (phantom-deps): Same-org sibling package in the Turfjs monorepo; phantom import pattern is stable across versions of this package. ai

Versions (showing 6 of 6)

Version Deps Published
7.3.5 8 / 9
7.3.4 8 / 9
7.3.3 8 / 9
7.3.2 8 / 9
7.3.1 8 / 9
7.3.0 8 / 10

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

2 findings
HIGH Publisher changed: mdfedderly → GitHub Actions (on 2026-02-08) provenance

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

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

2 findings
HIGH Publisher changed: mdfedderly → GitHub Actions (on 2026-01-28) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v7.3.1

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.

v7.3.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.