popper.js 0.3.0

[![Build Status](https://travis-ci.org/FezVrasta/popper.js.svg?branch=master)](https://travis-ci.org/FezVrasta/popper.js) [![npm version](https://badge.fury.io/js/popper.js.svg)](https://badge.fury.io/js/popper.js) [![Join the chat!](https://badges.gitter

popper.js@0.3.0 was published on 2016-04-08. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

All popper.js versions · Permanent reference to 0.3.0 · Latest release

Package specifications

Version0.3.0
License declarationMIT
Published2016-04-08T13:59:21.061Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
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 entrysrc/popper.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars15345
Repository forks1046

Install popper.js 0.3.0

npm install popper.js@0.3.0
pnpm add popper.js@0.3.0
yarn add popper.js@0.3.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

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-Review2/10 — Found 7/27 approved changesets -- score normalized to 2
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Maintained10/10 — 23 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
    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-Artifacts10/10 — no binaries found in the repo
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    License10/10 — license file detected
    Fuzzing0/10 — project is not fuzzed
    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