Repository navigation
Home
Yardenah PQ is the lab behind pqforge and pqcrypto.
pqforge is a pure-Dart, web-safe package for post-quantum application
workflows: encrypted files, folders, text, media, email payloads, records,
signed documents, signed webhooks, signed tokens, software artifacts,
gigabyte-scale streaming, multi-recipient envelopes, hybrid sessions, and
wrapped key custody — plus a universal CLI.
It is the application layer built on
pqcrypto (FIPS 203 ML-KEM, FIPS 204
ML-DSA, FIPS 205 SLH-DSA). See pqforge vs pqcrypto
for the boundary.
- CLI Guide — every command and flag
- Recipe Catalog — pick the surface for your app
-
Streaming And Large Files — gigabyte files,
pack/unpack - Multi-Recipient And Hybrid — one ciphertext for many; PQC + X25519
- Hybrid Sessions — X25519 + ML-KEM agreement, dual signatures
- HPKE — RFC 9180 seal, open, and export
- Key Custody — wrapped secret keys and stores
- Performance — engines, ciphers, measured throughput
- pqforge vs pqcrypto — which package to use
- Claim Boundary — what pqforge does and does not claim
export PQFORGE_PASSPHRASE='load-this-from-a-secret-manager'
# Emits the full keyset by default: ML-KEM + ML-DSA + SLH-DSA + X25519 + Ed25519 + ECDSA-P256.
dart run pqforge keygen --profile maximum --key-id vault --out-dir keys \
--passphrase-env PQFORGE_PASSPHRASE
# --hybrid adds an X25519 leg; large files auto-stream in bounded memory.
dart run pqforge encrypt-folder --hybrid \
--recipient-public keys/vault.kem.public.json \
--in-dir ./records --out-dir ./records.pqf
dart run pqforge decrypt-folder \
--recipient-secret keys/vault.kem.secret.wrapped.json \
--passphrase-env PQFORGE_PASSPHRASE \
--in-dir ./records.pqf --out-dir ./records.open- ML-KEM KEM-DEM envelopes (
.pqfone-shot,.pqfsstreaming). - ML-DSA signatures, plus hybrid ML-DSA + Ed25519/ECDSA-P256 and standalone ECDSA-P256.
hybrid-signalso accepts opt-in ECDSA-P384 and ECDSA-P521.compose-signis a separate 2-leg or 3-leg command. - SLH-DSA (FIPS 205, all 12 sets) composed into
keygen, custody, and detachedsign/verify(documents, text, media, webhooks, artifacts, tokens, logs, identity bindings). Not used for envelopes orhybrid-sign. It can be one opted-in leg ofcompose-sign. - AES-256-GCM and ChaCha20-Poly1305 AEAD on a pure-Dart or native engine.
- X25519 + ML-KEM hybrid key agreement, X448, P-256/P-384 ECDH for TLS hybrid groups, and P-521 ECDH for HPKE (
PqNistEcdh). P-521 ECDH is not a signature. - Bounded-memory gigabyte streaming and whole-folder
pack/unpack. - Multi-recipient envelopes — one sealed payload, key-wrapped per recipient.
- Argon2id + AES-GCM wrapped key custody (PBKDF2 under FIPS mode).
- Named recipes and a universal CLI (21 commands, plus
versionanduninstall) with AOT release binaries. File, folder, text, media, pack, unpack, sign, verify, hybrid-sign, compose-sign, ecdsa-sign, and cert commands are included. File commands report live progress (folder jobs include isolate-forwarded byte progress);--quietmutes per-file lines.
pqforge composes cryptographic building blocks for applications. It is not
a CMVP/FIPS 140 validated module, and it does not provide public-key trust,
identity vetting, replay stores, authorization policy, TLS, or legal workflow
policy. Its post-quantum security claim is inherited from pqcrypto. See
Claim Boundary.