pq-crystals/kyber
None observed · 2026-08-28
Health v2 · maintenance only
75/100
- Activity 95
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3373
- days_rel: n/a
- days_push: 31
- n_releases_24m: 0
Adoption not part of the score
1235 stars · 293 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The official reference implementation of the Kyber key encapsulation mechanism (ML-KEM), a NIST-standardized post-quantum KEM, written in C with an optimized AVX2 variant. The repository is no longer actively maintained and points users to mlkem-native for production use.
Use cases
- implement post-quantum key exchange in C
- benchmark ML-KEM key encapsulation performance
- study the reference implementation of Kyber
- test post-quantum KEM correctness with known-answer vectors
- evaluate AVX2-optimized lattice cryptography
When to choose
- you need the canonical reference implementation for research or verification
- you want to study how Kyber/ML-KEM works at the algorithm level
- you need a simple, readable C implementation for prototyping
When to avoid
- you need production-quality, maintained code - use mlkem-native instead
- you require formally verified or side-channel-hardened implementations - use mlkem-libjade
- you need long-term security support for a deployed system
Facets
library · maturity abandoned
cryptography security cpp post-quantum-cryptography key-encapsulation-mechanism ml-kem lattice-based reference-implementation avx2 linux macos
1 source
- readme: https://github.com/pq-crystals/kyber · fetched 2026-08-28 · 2d13334f3cc1
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| pq-crystals/kyber | main | 75 |
For agents
markdown · JSON · MCP: product_card(name="pq-crystals/kyber")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem