@react-three/drei

useful add-ons for react-three-fiber

@react-three/drei@10.7.9 was published on 2026-09-25. Its manifest declares 21 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @react-three/drei versions · Permanent reference to 10.7.9

Package specifications

Version10.7.9
License declarationMIT
Published2026-09-25T15:34:13.763Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count21
Peer requirement count4
Optional dependency count0
Minified size1641.01 KiB
Minified + gzip509.28 KiB
Unpacked distribution size1712.59 KiB
Published file count483
Package typeNot declared
ES module entryindex.js
Default entryindex.cjs.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies52
Repository stars10053
Repository forks859

Install @react-three/drei 10.7.9

npm install @react-three/drei@10.7.9
pnpm add @react-three/drei@10.7.9
yarn add @react-three/drei@10.7.9

Runtime dependencies

Peer requirements

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.

Code-Review1/10 — Found 3/30 approved changesets -- score normalized to 1
Maintained5/10 — 4 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 5
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
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-Artifacts9/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Security-Policy0/10 — security policy file not detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness