popper_js
RubyGemsv2.11.8Not recommended for new projects
No — popper_js should not be adopted for new projects. Last published 1123 days ago.
- AAdoption: grade A, Excellent.
8M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 1123 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding popper_js to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Ruby
- No constraint declared
Used by
Popular packages that depend on popper_js.
Relationship graph
Dependencies (left) and dependents (right) of popper_js.
Release history
No releases in the last two years, typically about 60 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.11.8latest | 3 years ago | — | MIT |
| 2.11.7 | 3 years ago | — | MIT |
| 2.11.6 | 4 years ago | — | MIT |
| 1.16.1 | 4 years ago | — | MIT |
| 2.11.5 | 4 years ago | — | MIT |
| 2.9.3 | 5 years ago | — | MIT |
| 2.9.2 | 5 years ago | — | MIT |
| 2.8.6 | 5 years ago | — | MIT |
| 2.6.0 | 5 years ago | — | MIT |
| 1.16.0 | 6 years ago | — | MIT |
| 1.15.0 | 6 years ago | — | MIT |
| 1.14.7 | 6 years ago | — | MIT |
| 1.14.5 | 7 years ago | — | MIT |
| 1.14.3 | 8 years ago | — | MIT |
| 1.12.9 | 8 years ago | — | MIT |
Overview
popper_js is an RubyGems package. It is extremely widely used, with about 8M downloads per week and 1 known dependents in the graph. The latest version is 2.11.8, released under the MIT license.
Who should use it
Teams working in the RubyGems ecosystem who need this functionality and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your RubyGems stack.
Pros
- Large, well-established user base (8M weekly downloads).
- Clear open-source license (MIT).
- Zero runtime dependencies — minimal footprint.
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use popper_js?
No — popper_js should not be adopted for new projects. Last published 1123 days ago.
How do I install popper_js?
Run `gem install popper_js` to add popper_js to your RubyGems project.
What license is popper_js released under?
popper_js is distributed under the MIT license.
How popular is popper_js?
popper_js has approximately 8,003,664 downloads per week and 1 known dependent packages.
Is popper_js still maintained?
The most recent release of popper_js (v2.11.8) was published 3 years ago.