react-intersection-observer 0.2.12

Monitor if a component is inside the viewport, using IntersectionObserver API

react-intersection-observer@0.2.12 was published on 2017-05-24. Its manifest declares 2 runtime dependencies and 2 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All react-intersection-observer versions · Permanent reference to 0.2.12 · Latest release

Package specifications

Version0.2.12
License declarationMIT
Published2017-05-24T13:20:56.205Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies28
Repository stars5540
Repository forks189

Install react-intersection-observer 0.2.12

npm install react-intersection-observer@0.2.12
pnpm add react-intersection-observer@0.2.12
yarn add react-intersection-observer@0.2.12

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.

Maintained10/10 — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
Code-Review0/10 — Found 1/20 approved changesets -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- 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
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Packaging10/10 — packaging workflow detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness