@node-rs/bcrypt-win32-x64-msvc 1.4.2

Rust bcrypt binding

@node-rs/bcrypt-win32-x64-msvc@1.4.2 was published on 2021-10-22. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 10.

All @node-rs/bcrypt-win32-x64-msvc versions · Permanent reference to 1.4.2 · Latest release

Package specifications

Version1.4.2
License declarationMIT
Published2021-10-22T06:32:50.470Z
Node.js requirement>= 10
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size264.42 KiB
Published file count3
Package typeNot declared
ES module entryNot declared
Default entrybcrypt.win32-x64-msvc.node
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars1481
Repository forks52

Install @node-rs/bcrypt-win32-x64-msvc 1.4.2

npm install @node-rs/bcrypt-win32-x64-msvc@1.4.2
pnpm add @node-rs/bcrypt-win32-x64-msvc@1.4.2
yarn add @node-rs/bcrypt-win32-x64-msvc@1.4.2

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

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