Menu

Individual skill

jwt-security-hardener

0upvotes

Audits JSON Web Token implementations for algorithm confusion attacks, key rotation, expiration, and replay defense.',

skills/security/jwt-security-hardener/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Audit and harden JSON Web Token (JWT) authentication, signing, and verification pipelines to eliminate critical vulnerabilities: algorithm confusion (`alg: none`, HMAC vs RSA/ECDSA confusion), weak signing secrets, missing claim validations, and lack of revocation mechanisms.

## When to Use

- Implementing or reviewing JWT authentication for APIs, single sign-on, or microservices.
- Passing security audits and penetration tests on token validation logic.
- Setting up token rotation, refresh token revocation, and asymmetric key pairs (JWKS).

## What to Analyze

1. **Algorithm Whitelisting**: Explicitly enforcing expected algorithms (e.g. `algorithms: ['RS256']`) preventing `none` or public-key-as-HMAC attacks.
2. **Mandatory Standard Claims**: Enforcing `exp` (short expiration, max 15m), `iat`, `nbf`, `iss` (issuer validation), and `aud` (audience validation).