</>PackageGraphPackageGraph

bcrypt

RubyGemsv3.1.22

Safe to adopt

Yes — bcrypt scores well across adoption, maintenance, weight, supply chain, and licensing. 103M downloads per week and 1 known dependents. Last published 175 days ago. 2 releases in the last 2 years.

  • AAdoption: grade A, Excellent.

    103M downloads per week and 1 known dependents.

  • BMaintenance: grade B, Good.

    Last published 175 days ago. 2 releases in the last 2 years.

  • 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 bcrypt to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

—
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Ruby
No constraint declared

Used by

Popular packages that depend on bcrypt.

deviseRubyGems

No description provided.

↓ 73.6M/wk◈ 0 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of bcrypt.

devisebcrypt
bcrypt dependencies dependents

Frequently installed together

railtiesRubyGems

No description provided.

↓ 195.9M/wk◈ 5 dependents⚖ MIT
respondersRubyGems

No description provided.

↓ 83.3M/wk◈ 1 dependents⚖ MIT
wardenRubyGems

No description provided.

↓ 76.3M/wk◈ 1 dependents⚖ MIT
orm_adapterRubyGems

No description provided.

↓ 71.3M/wk◈ 1 dependents⚖ MIT

Release history

2 releases in the last two years, typically about 148 days apart.

Recent versions of bcrypt
VersionPublishedSizeLicense
3.1.22latest5 months ago—MIT
3.1.218 months ago—MIT
3.1.202 years ago—MIT
3.1.193 years ago—MIT
3.1.184 years ago—MIT
3.1.174 years ago—MIT
3.1.166 years ago—MIT
3.1.156 years ago—MIT
3.1.146 years ago—MIT
3.1.137 years ago—MIT
3.1.128 years ago—MIT
3.1.1110 years ago—MIT
3.1.1011 years ago—MIT
3.1.912 years ago—MIT
3.1.812 years ago—MIT

Overview

bcrypt is an RubyGems package. It is extremely widely used, with about 103M downloads per week and 1 known dependents in the graph. The latest version is 3.1.22, 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 (103M 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

Coda Hale

Frequently asked questions

Should I use bcrypt?

Yes — bcrypt scores well across adoption, maintenance, weight, supply chain, and licensing. 103M downloads per week and 1 known dependents. Last published 175 days ago. 2 releases in the last 2 years.

How do I install bcrypt?

Run `gem install bcrypt` to add bcrypt to your RubyGems project.

What license is bcrypt released under?

bcrypt is distributed under the MIT license.

How popular is bcrypt?

bcrypt has approximately 103,010,699 downloads per week and 1 known dependent packages.

Is bcrypt still maintained?

The most recent release of bcrypt (v3.1.22) was published 5 months ago.