dcodeio/bcrypt.js

Optimized bcrypt in JavaScript with zero dependencies, with TypeScript support.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 18th, 2026
Created on May 1st, 2013
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 290
Total Stargazers: 3,797 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.9 days
Mean response time: 85.2 days
90th percentile: 215.3 days
Tracked items: 41

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 51 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (45)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

bcrypt.js is a JavaScript implementation of the bcrypt password hashing algorithm that operates with zero external dependencies and includes TypeScript support.

The tool addresses the need for secure password hashing in JavaScript environments where native bcrypt libraries may not be available or practical. It implements the bcrypt algorithm directly in JavaScript, allowing developers to hash and verify passwords without relying on compiled native modules or external services. This approach makes it portable across different JavaScript runtimes and eliminates installation complexity associated with native bindings.

Developers should choose this implementation when working in pure JavaScript or TypeScript environments where native bcrypt bindings are unavailable, impractical, or undesirable. It suits projects that need password hashing without adding native dependencies, including browser-based applications, serverless functions, and environments with restricted compilation capabilities. The zero-dependency design means no additional packages need to be installed or maintained alongside the core functionality.

The project maintains a stable codebase with infrequent but deliberate updates. Issues and pull requests receive responses, indicating active maintenance and engagement with user concerns. The development activity reflects a mature project focused on reliability rather than rapid feature expansion.