BCrypt.Net-Next.StrongName

v4.2.1

A fixed, enhanced and namespace compatible version of BCrypt.Net port of jBCrypt implemented in C#. It uses a variant of the Blowfish encryption algorithm’s keying schedule, and introduces a work factor, which allows you to determine how expensive the hash function will be, allowing the algorithm to be "future-proof".

ChrisMcKee

bcrypt BCrypt.Net cryptography hashing password security hash crypto blowfish gdpr

NuGet Stats Changelog

Total Downloads

513.6K

513,597

Published

Jan 1, 1900

Latest stable version

Install

.NET CLI

dotnet add package BCrypt.Net-Next.StrongName --version 4.2.1

Package Manager Console

Install-Package BCrypt.Net-Next.StrongName -Version 4.2.1

PackageReference

<PackageReference Include="BCrypt.Net-Next.StrongName" Version="4.2.1" />

Frameworks

net10.0 .NETFramework4.6.2 .NETFramework4.7.2 .NETFramework4.8 .NETStandard2.0 .NETStandard2.1

Dependencies

System.Memory

.NETFramework4.6.2

[4.6.3, )

System.Memory

.NETFramework4.7.2

[4.6.3, )

System.Memory

.NETFramework4.8

[4.6.3, )

System.Memory

.NETStandard2.0

[4.6.3, )

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.

This version is unlisted. Prefer a listed release unless you deliberately need this exact version for reproducibility.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.

Audit NuGet dependencies in a .NET project Review NuGet licenses before shipping