← Home

@turf/sample

npm Repository Homepage

Takes a FeatureCollection and returns a FeatureCollection with given number of features at random.

6
Versions
MIT
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

geojsonstatssampleturf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance for the Turfjs monorepo. ai
publish-pattern dormant-publish AI (publish-pattern): Turfjs monorepo publishes in batches; dormancy reflects release cadence, not compromise. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dep used by TypeScript compilation. ai
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): Type-only dependency; not directly imported at runtime. ai

Versions (showing 6 of 6)

Version Deps Published
7.3.5 3 / 7
7.3.4 3 / 7
7.3.3 3 / 7
7.3.2 3 / 7
7.3.1 3 / 7
7.3.0 3 / 8

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. Consider requesting the maintainer enable provenance via CI/CD.

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.