Roadmap
What is shipped, what is next, and what is explicitly not promised yet.
Shipped — v1.0
- PFX/P12 → PEM with key-match verification
- PEM → PFX with mismatch protection and honest compatibility notes
- Certificate decoder (PEM + DER) with raw JSON view
- CSR decoder with signature verification and requested SANs
- Key ↔ certificate match (modulus + sign/verify)
- Chain order with missing-issuer detection
- DER & JWK inspector with private-material warnings
All of it RSA-first, browser-local, and covered by an automated test harness.
Planned — in rough order
EC & Ed25519 support (v1.1)
The single most requested direction. RSA is fully covered today; EC/Ed25519 X.509 and PKCS#12 objects currently produce a clear unsupported error. The plan is an in-browser fallback that handles the same local-only guarantee.
Batch mode
Convert or decode many files in one session with per-file results — still without uploading anything.
Offline / desktop packaging
The whole site already works offline once loaded; a packaged build (PWA and a downloadable single-file version) would make that explicit and let you keep a copy next to your sensitive files.
CLI or scripted use
A command-line version of the same parsing core for automation — after the browser tools are complete.
More PKCS#12 write options
Optional AES-256 MAC and encrypted certificate bags for the PEM → PFX path, moving beyond the current SHA-1 MAC + unencrypted cert bags limitation.
No dates, no promises: items move when they are proven and tested. That is also why EC support reports an honest error today instead of silently doing the wrong thing.
Not planned
- Uploading or server-side processing of keys — that would defeat the point.
- Accounts, subscriptions, ads or tracking.
- Claiming to be a certificate authority, a validator of trust chains, or a security audit.