Kemforge - The Quantum-Safe curl: Test and verify ML-KEM/PQC endpoints.

We’ve all been hearing about the transition to Post-Quantum Cryptography (PQC), but as developers, we’ve had a major visibility problem. I built Kemforge because I was tired of the 'False Positive' trap. Most of us use curl to test our APIs, but standard tools often silently fall back to classical encryption without telling you. In an era where 'Harvest Now, Decrypt Later' (HNDL) is a real threat to our data privacy, 'just connecting' isn't enough anymore—we need to know how we are connecting. Kemforge is a diagnostic-first CLI tool designed for the 2026 security landscape: Quantum-Safe by Default: It carries its own TLS stack with native support for ML-KEM (FIPS 203). It doesn’t matter if your OS libraries are outdated; Kemforge stays current. Instant Verification: It gives you a clear 'Quantum-Safe' vs. 'Vulnerable' status in the terminal before the response body even loads. Backend Agnostic: Whether your API is Go, Rust, Python, Java, or Node.js, Kemforge verifies the handshake at the protocol level. Drop-in Compatibility: It supports the curl flags you already know, making it easy to swap into your local dev loop or CI/CD pipelines. I’m on a mission to help companies make their infrastructure truly future-proof. If you’re currently navigating a PQC migration or just want to make sure your user data is safe from future decryption, I’d love for you to give Kemforge a spin. I’ll be here all day to answer questions about the implementation, PQC standards, or how to gate your pipelines against security regressions! What’s your team’s strategy for the quantum transition? Let’s chat in the comments! 👇"