@react-three/drei 3.1.0

useful add-ons for react-three-fiber

@react-three/drei@3.1.0 was published on 2021-01-29. Its manifest declares 12 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 3.1.0 · Latest release

Package specifications

Version	3.1.0
License declaration	MIT
Published	2021-01-29T18:06:49.267Z
Node.js requirement	Not declared
Type declarations	Bundled declarations
Runtime dependency count	12
Peer requirement count	4
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	713.67 KiB
Published file count	146
Package type	Not declared
ES module entry	index.js
Default entry	index.cjs.js
Side effects declaration	false
Direct advisories	0
Resolved graph dependencies	20
Repository stars	10053
Repository forks	859

Install @react-three/drei 3.1.0

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

Runtime dependencies

zustand ^3.0.3
stats.js ^0.17.0
detect-gpu ^3.0.0
glsl-noise ^0.0.0
lodash.omit ^4.5.0
lodash.pick ^4.4.0
blob-polyfill ^4.0.20200601
utility-types ^3.10.0
@babel/runtime ^7.11.2
react-merge-refs ^1.0.0
@react-spring/web ^9.0.0-rc.3
troika-three-text ^0.38.0

Peer requirements

react >=16.13
three >=0.125.0
react-dom >=16.13 (optional peer)
react-three-fiber >=5.0

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-Review	1/10 — Found 3/30 approved changesets -- score normalized to 1
Maintained	5/10 — 4 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 5
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts	9/10 — binaries present in source code
Pinned-Dependencies	0/10 — dependency not pinned by hash detected -- score normalized to 0
License	10/10 — license file detected
Security-Policy	0/10 — security policy file not detected
Branch-Protection	0/10 — branch protection not enabled on development/release branches
Fuzzing	0/10 — project is not fuzzed
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/%40react-three%2Fdrei/3.1.0 — retrieved 2026-10-31T18:57:18.200Z
https://api.deps.dev/v3/projects/github.com%2Fpmndrs%2Fdrei — retrieved 2026-10-31T14:08:17.722Z
https://api.deps.dev/v3/systems/npm/packages/%40react-three%2Fdrei/versions/3.1.0 — retrieved 2026-10-31T18:57:18.655Z
https://api.deps.dev/v3/systems/npm/packages/%40react-three%2Fdrei/versions/3.1.0:dependencies — retrieved 2026-10-31T18:57:18.671Z