three-mesh-bvh

A BVH implementation to speed up raycasting against three.js meshes.

three-mesh-bvh@0.9.17 was published on 2026-10-28. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All three-mesh-bvh versions · Permanent reference to 0.9.17

Package specifications

Version0.9.17
License declarationMIT
Published2026-10-28T08:05:16.288Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified size92.01 KiB
Minified + gzip27.97 KiB
Unpacked distribution size2277.20 KiB
Published file count102
Package typemodule
ES module entrysrc/index.js
Default entrybuild/index.umd.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars3525
Repository forks341

Install three-mesh-bvh 0.9.17

npm install three-mesh-bvh@0.9.17
pnpm add three-mesh-bvh@0.9.17
yarn add three-mesh-bvh@0.9.17

Runtime dependencies

  • None declared

Peer requirements

Optional dependencies

  • None declared

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.

Code-Review0/10 — Found 1/13 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST10/10 — SAST tool is run on all commits

Evidence and freshness