rspec-core
RubyGemsv3.13.6Safe to adopt
Yes — rspec-core scores well across adoption, maintenance, weight, supply chain, and licensing. 297.8M downloads per week. Last published 325 days ago. 5 releases in the last 2 years.
- AAdoption: grade A, Excellent.
297.8M downloads per week.
- BMaintenance: grade B, Good.
Last published 325 days ago. 5 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package.
- ASupply chain: grade A, Excellent.
No install scripts, 4 maintainers, and a contained dependency surface.
- 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 rspec-core 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.
Licenses in the dependency tree
Every license you inherit by installing rspec-core, not just its own. Check this before a legal review, not after.
Compatibility
- Ruby
- No constraint declared
Dependencies
Declared by rspec-core v3.13.6. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Relationship graph
Dependencies (left) and dependents (right) of rspec-core.
Release history
4 releases in the last two years, typically about 100 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.13.6latest | 10 months ago | — | MIT |
| 3.13.5 | 1 year ago | — | MIT |
| 3.13.4 | 1 year ago | — | MIT |
| 3.13.3 | 1 year ago | — | MIT |
| 3.13.2 | 1 year ago | — | MIT |
| 3.13.1 | 2 years ago | — | MIT |
| 3.13.0 | 2 years ago | — | MIT |
| 3.12.3 | 2 years ago | — | MIT |
| 3.12.2 | 3 years ago | — | MIT |
| 3.12.1 | 3 years ago | — | MIT |
| 3.12.0 | 3 years ago | — | MIT |
| 3.11.0 | 4 years ago | — | MIT |
| 3.10.2 | 4 years ago | — | MIT |
| 3.10.1 | 5 years ago | — | MIT |
| 3.10.0 | 5 years ago | — | MIT |
Overview
rspec-core is an RubyGems package. It is extremely widely used, with about 297.8M downloads per week. The latest version is 3.13.6, 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 (297.8M weekly downloads).
- Clear open-source license (MIT).
- Lean dependency tree (1 direct dependencies).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use rspec-core?
Yes — rspec-core scores well across adoption, maintenance, weight, supply chain, and licensing. 297.8M downloads per week. Last published 325 days ago. 5 releases in the last 2 years.
How do I install rspec-core?
Run `gem install rspec-core` to add rspec-core to your RubyGems project.
How many dependencies does rspec-core have?
rspec-core declares 1 direct dependency and pulls in 1 packages in total once its runtime tree is resolved.
What license is rspec-core released under?
rspec-core is distributed under the MIT license.
How popular is rspec-core?
rspec-core has approximately 297,753,325 downloads per week.
Is rspec-core still maintained?
The most recent release of rspec-core (v3.13.6) was published 10 months ago.