Skip to main content
PCLCrypto package icon

PCLCrypto

PCL Crypto provides a consistent, portable set of crypto APIs for .NET 4.5, Windows Phone 8.0 SL & 8.1 Xaml, Windows Store, Xamarin.iOS, Xamarin.Android. This makes it easier to create cross-platform .NET libraries and apps. Crypto functionality includes asymmetric and symmetric encryption and signatures, and key derivation. PCLCrypto calls into each native platform's crypto API for maximum performance. For RSA operations this produces a 2-100X improvement in performance on Android and iOS over using the standard RSACryptoServiceProvider API.

Total Downloads
8.0M
7,971,429
Published
Oct 5, 2018
Latest stable version

Install

.NET CLI
dotnet add package PCLCrypto --version 2.1.32-alpha
Package Manager Console
Install-Package PCLCrypto -Version 2.1.32-alpha
PackageReference
<PackageReference Include="PCLCrypto" Version="2.1.32-alpha" />

Frameworks

.NETCoreApp1.0 .NETFramework4.5 .NETPortable0.0-Profile259 .NETPortable0.0-Profile32 .NETStandard1.0 MonoAndroid2.3 WindowsPhone8.0 Xamarin.iOS1.0

Dependencies

[1.0.5, )
PInvoke.NCrypt
.NETCoreApp1.0
[0.5.126, )
[4.3.0, )
Validation
.NETCoreApp1.0
[2.4.15, )
PInvoke.NCrypt
.NETFramework4.5
[0.5.126, )
Validation
.NETFramework4.5
[2.4.15, )
Validation
.NETPortable0.0-Profile259
[2.4.15, )
PInvoke.NCrypt
.NETPortable0.0-Profile32
[0.5.126, )
Validation
.NETPortable0.0-Profile32
[2.4.15, )
NETStandard.Library
.NETStandard1.0
[1.6.1, )
Validation
.NETStandard1.0
[2.4.15, )
PInvoke.NCrypt
MonoAndroid2.3
[0.5.126, )
Validation
MonoAndroid2.3
[2.4.15, )
Validation
WindowsPhone8.0
[2.4.15, )
PInvoke.NCrypt
Xamarin.iOS1.0
[0.5.126, )
Validation
Xamarin.iOS1.0
[2.4.15, )

Adoption guide

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

This version is marked prerelease. Validate its API and upgrade path before production use.

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

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

The published metadata declares 17 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.