Tracking issue for the release of `hqc-kem`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 111
- Forks
- 53
- Avg merge
- 5d 29m
- Merged PRs (30d)
- 2
Description
An initial PR for HQC landed just a week ago (#281). Thank you for your work on this!
I see from the PR discussion that even if it was merged, there are some remaining topics to be discussed and resolved. I wanted to open an issue both to let people track the future release of hqc-kem, and see what remains before we get there.
The only currently usable implementation of HQC in Rust is pqcrypto-hqc, and that was marked as unmaintained just yesterday: RUSTSEC-2026-0164. This is what made me to look at the latest status of RustCrypto's alternative. (A relevant side note is that pqcrypto-hqc and hqc-kem implements different versions of the HQC spec, and are not directly compatible)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the initial HQC implementation PR #281 and its discussion, then identify the remaining topics before releasing hqc-kem. Done means those unresolved topics are settled and the release can proceed; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100