JWT Inspector & Playground
Decode, verify, live-edit, and re-sign JWTs in the browser — inspect claims and timestamps, and flag weak algorithms, alg:none, and expiry. Nothing is uploaded.
Proposed stack
- Next.js
- TypeScript
- Tailwind CSS
- jose
Goal
Give auth developers a fast, private way to inspect and debug JSON Web Tokens.
Overview
Paste a JWT and the tool decodes the header, payload, and signature, showing standard claims with human-readable timestamps and expiry/not-yet-valid warnings.
Verify the signature against a supplied secret (HS) or public key/JWK (RS/ES), and flag dangerous cases like alg:none or weak secrets.
Live-edit the header or payload and re-sign with a test key to produce a new token — all in the browser, nothing uploaded.
Architecture
JWT → Decode → Inspect Claims → Verify / Re-sign
Key features
- Decode header, payload, and signature.
- Human-readable standard claims + expiry warnings.
- Verify signatures (HS/RS/ES) against a secret or JWK.
- Flag alg:none and weak algorithms.
- Live-edit and re-sign with a test key.
- 100% client-side — nothing uploaded.
Technical challenges
- Supporting HS/RS/ES verification cleanly with a single UI.
- Surfacing dangerous cases (alg:none, weak secrets, expiry) clearly.
- Keeping crypto fully client-side with the jose library.
How it's built
- 1Next.js + TypeScript + Tailwind, using jose for all JWT crypto.
- 2Decode/verify/re-sign flows with live editing.
- 3Verified end to end in the browser.
Interested in this work?
Happy to talk through the design, trade-offs, and implementation plan.