Skip to main content
BCrypt.Net-Next package icon

BCrypt.Net-Next

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.

Total Downloads
60.6M
60,559,304
Published
Mar 21, 2017
Latest stable version

Install

.NET CLI
dotnet add package BCrypt.Net-Next --version 2.1.1
Package Manager Console
Install-Package BCrypt.Net-Next -Version 2.1.1
PackageReference
<PackageReference Include="BCrypt.Net-Next" Version="2.1.1" />

Frameworks

.NETFramework2.0 .NETFramework3.5 .NETStandard1.6 .NETStandard1.3 .NETFramework4.5 .NETFramework4.0 .NETFramework4.5.1 .NETFramework4.6.2 .NETFramework4.5.2 .NETCoreApp1.0 .NETCoreApp1.1

Dependencies

[4.3.0, )
System.Net.Primitives
.NETStandard1.6
[4.3.0, )
NETStandard.Library
.NETStandard1.6
[1.6.1, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
System.Net.Primitives
.NETStandard1.3
[4.3.0, )
NETStandard.Library
.NETStandard1.3
[1.6.1, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[1.0.4, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[4.3.0, )
[1.1.1, )
[4.3.0, )
[4.3.0, )
[4.3.0, )

Adoption guide

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

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

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

The published metadata declares 31 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

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.