Skip to main content

Pipeline Test Coverage Documentation

CryptoDataHub is a repository of cryptography-related data available under a free license. The main goal of the repository is to support cryptographic library tester and client/server cryptographic settings analyzer applications such as CryptoLyzer with reliable and freely available data.

Use CryptoDataHub when you need algorithm identifiers — public key, digital signature, key exchange, block cipher, stream cipher, cryptographic hash, elliptic-curve, and message authentication code algorithms are available as enumerations with their code points, names, and parameters.

Use CryptoDataHub when you need Diffie-Hellman parameters — both the finite field parameters defined by RFC 2539, RFC 3526, RFC 5114, and RFC 7919, and the ones built into Apache HTTP Server, HAProxy, Postfix, ProFTPD, and socat.

Use CryptoDataHub when you need trust stores — the trusted root certification authority certificate stores of Android, Apple, Google Chrome, Microsoft, Mozilla, OpenJDK, and Oracle, and the Certificate Transparency log list.

Use CryptoDataHub when you need vulnerability data — the algorithms and parameters affected by D(HE)at, Logjam, Sweet32, Shatter, and Weak DH are marked in the data itself.

The strength of CryptoDataHub is that the data is machine-readable, versioned, and updated from its original sources by the updaters shipped with the repository, so a consumer does not have to scrape registries, vendor pages, or trust store exports on its own.

Why CryptoDataHub?

  • Free license — the data is available under the same license as the code, without a per-consumer agreement.
  • One source for several protocols — protocol-independent algorithm data and the protocol-dependent attributes of IKE, SSL, TLS, SSH, and DNSSEC live in one repository.
  • Wrapper included — the data ships with a Python wrapper, so it can be consumed as typed enumerations instead of as raw JSON.
  • Reproducible updates — update-ct-log, update-oqs and update-trust-stores regenerate the data from its original sources.

Usage

uv

uv add cryptodatahub
from cryptodatahub.tls.algorithm import TlsCipherSuite

# look up a cipher suite by its code point
TlsCipherSuite.from_code(0x1301)
# TlsCipherSuite.TLS_AES_128_GCM_SHA256

Support

Python implementations

  • CPython 3.9+
  • PyPy 3.9+

Operating systems

  • Linux
  • macOS
  • Windows

Documentation

Detailed documentation is available on the project's Read the Docs site.

License

The code is available under the terms of Mozilla Public License Version 2.0 (MPL 2.0).

A non-comprehensive but straightforward description of MPL 2.0 can be found at the Choose an open source license website.

Credits

Metadata

Release files for CryptoDataHub 1.6.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for CryptoDataHub 1.6.1
File Size Uploaded Provenance
cryptodatahub-1.6.1.tar.gz 718.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for CryptoDataHub 1.6.1
File Interpreter ABI Platform
cryptodatahub-1.6.1-py3-none-any.whl Python 3 none any Details

Total release size: 1.3 MB

Release files / cryptodatahub-1.6.1.tar.gz

Download URL cryptodatahub-1.6.1.tar.gz
Size 718.1 kB
Tags Source
SHA-256 checksum
How to use checksums
fcbab0de3708811ec7228c7c690f679423ecd235b42b15f6a1bc9a0d2ecf0535
BLAKE2b-256 checksum
How to use checksums
e4339923754c0aa947442f43a66b38a58301be06726155632596ba31650f2ff4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.7

Release files / cryptodatahub-1.6.1-py3-none-any.whl

Download URL cryptodatahub-1.6.1-py3-none-any.whl
Size 629.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
706308cda93ac679d3049f44467d8f5e7741c518d614f2ff11e4cc6480732fd5
BLAKE2b-256 checksum
How to use checksums
59f3f80a9757cea05e94652b8d13bd0eb8c0189196801bafec30b496ee3bef70
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.7

Security for CryptoDataHub 1.6.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page