@node-rs/bcrypt 1.2.2

Rust bcrypt binding

@node-rs/bcrypt@1.2.2 was published on 2021-06-01. Its manifest declares 13 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 10.

All @node-rs/bcrypt versions · Permanent reference to 1.2.2 · Latest release

Package specifications

Version1.2.2
License declarationMIT
Published2021-06-01T01:52:58.595Z
Node.js requirement>= 10
Type declarationsBundled declarations
Runtime dependency count13
Peer requirement count0
Optional dependency count12
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.72 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository stars1481
Repository forks52

Install @node-rs/bcrypt 1.2.2

npm install @node-rs/bcrypt@1.2.2
pnpm add @node-rs/bcrypt@1.2.2
yarn add @node-rs/bcrypt@1.2.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

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-Review0/10 — Found 0/21 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness