This release is a pre-release and may not be stable for production use.
Swarmauri Cipher Suite FIPS 203
Cipher suite bindings for the post-quantum ML-KEM key encapsulation mechanisms standardised in NIST FIPS 203.
Features
- Enumerates the ML-KEM-512, ML-KEM-768, and ML-KEM-1024 parameter sets
- Describes NIST security level metadata for downstream policy enforcement
- Normalises wrap / unwrap requests with provider-oriented descriptors
- Ships entry-point metadata for seamless Swarmauri component discovery
Installation
pip
pip install swarmauri_cipher_suite_fips203
Poetry
poetry add swarmauri_cipher_suite_fips203
uv
To add the dependency to a pyproject.toml managed by uv:
uv add swarmauri_cipher_suite_fips203
Or install it into the active environment:
uv pip install swarmauri_cipher_suite_fips203
Usage
from swarmauri_cipher_suite_fips203 import Fips203CipherSuite
suite = Fips203CipherSuite(name="mlkem")
# Describe a ML-KEM-768 key encapsulation request
descriptor = suite.normalize(op="wrap", alg="ML-KEM-768")
print(descriptor["constraints"]["nistLevel"]) # -> 3
print(descriptor["mapped"]["provider"]) # -> ml-kem:ML-KEM-768
The suite raises ValueError if a non-ML-KEM algorithm is requested, allowing
callers to surface the policy violation immediately.
Entry Point
The suite registers under the swarmauri.cipher_suites entry point as
Fips203CipherSuite.
Want to help?
If you want to contribute to swarmauri-sdk, read up on our guidelines for contributing that will help you get started.
Metadata
Release files for swarmauri_cipher_suite_fips203 0.11.0.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| swarmauri_cipher_suite_fips203-0.11.0.dev2.tar.gz | 3.5 kB | Without provenance | Details for swarmauri_cipher_suite_fips203-0.11.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| swarmauri_cipher_suite_fips203-0.11.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for swarmauri_cipher_suite_fips203-0.11.0.dev2-py3-none-any.whl |
Total release size: 7.7 kB
Release files / swarmauri_cipher_suite_fips203-0.11.0.dev2.tar.gz
| Download URL | swarmauri_cipher_suite_fips203-0.11.0.dev2.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f69d6fbd66dc598247f7494f0c2f0ea0248ce06f08dece70d0433f531db31b53
|
|
BLAKE2b-256 checksum How to use checksums |
bd96b480c4de119e70857f3dfa524a3d1740630581c03af0371cdd3ab9480583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / swarmauri_cipher_suite_fips203-0.11.0.dev2-py3-none-any.whl
| Download URL | swarmauri_cipher_suite_fips203-0.11.0.dev2-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2ed1a69041db2f3ada821efefcba6da6ad9748032353316baef10039c9ea9ba
|
|
BLAKE2b-256 checksum How to use checksums |
164f2638889021f7065be1e2bcb1f5c523cc8c4d1294e717a074c50fdf79efcb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for swarmauri_cipher_suite_fips203 0.11.0.dev2
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.