@turf/nearest-neighbor-analysis

Calculates an index based the average distances between points in the dataset, thereby providing inference as to whether the data is clustered, dispersed, or randomly distributed within the study area.

@turf/nearest-neighbor-analysis@7.4.0 was published on 2026-08-03. Its manifest declares 10 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @turf/nearest-neighbor-analysis versions · Permanent reference to 7.4.0 · View npm registry JSON

Package specifications

Version7.4.0
License declarationMIT
Published2026-08-03T15:31:13.349Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count10
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size34.82 KiB
Published file count9
Package typemodule
ES module entrydist/esm/index.js
Default entrydist/cjs/index.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies12
Repository stars10527
Repository forks1027

Install @turf/nearest-neighbor-analysis 7.4.0

npm install @turf/nearest-neighbor-analysis@7.4.0
pnpm add @turf/nearest-neighbor-analysis@7.4.0
yarn add @turf/nearest-neighbor-analysis@7.4.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Code-Review0/10 — Found 1/27 approved changesets -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Pinned-Dependencies10/10 — all dependencies are pinned
Fuzzing10/10 — project is fuzzed
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness