@bjoerge/react-popper 0.9.2

React wrapper around PopperJS.

@bjoerge/react-popper@0.9.2 was published on 2018-04-04. Its manifest declares 2 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @bjoerge/react-popper versions · Permanent reference to 0.9.2 · View npm registry JSON · Latest release

Package specifications

Version0.9.2
License declarationMIT
Published2018-04-04T13:56:02.079Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size141.46 KiB
Published file count18
Package typeNot declared
ES module entrylib/react-popper.js
Default entrydist/react-popper.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars2483
Repository forks229

Install @bjoerge/react-popper 0.9.2

npm install @bjoerge/react-popper@0.9.2
pnpm add @bjoerge/react-popper@0.9.2
yarn add @bjoerge/react-popper@0.9.2

Runtime dependencies

Peer requirements

  • react 0.14.x || ^15.0.0 || ^16.0.0
  • react-dom 0.14.x || ^15.0.0 || ^16.0.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.

Maintained0/10 — project is archived
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review5/10 — Found 15/28 approved changesets -- score normalized to 5
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness