Recordsgolanggithub.com/golang-jwt/jwt/v5v5.3.1jwt.ClaimsValidator
Published samples
- github.com/golang-jwt/jwt/v5 v5.3.1: Enforce custom validation and require expiration checks during jwt/v5 token parsing This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWjwt.ParseWithClaimsjwt.ClaimsValidatorjwt.WithExpirationRequiredgo MIT-0 · 2026-08-17
- github.com/golang-jwt/jwt/v5 v5.3.1: Validate custom claims in golang-jwt v5 using ClaimsValidator instead of the silently ignored v4 Valid method This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWjwt.ParseWithClaimsjwt.ClaimsValidatorjwt.RegisteredClaimsjwt.ErrTokenInvalidClaimsjwt.WithValidMethodsjwt.WithExpirationRequiredgo MIT-0 · 2026-08-17
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux musl · docker
Observations: PROJECT_TEST 1✓ 1✕ — Verified: CONTRACT 5✓ 1✕
|
MEDIUM | 2 | 6 | 82% | 1 · 3✓ | 2026-09-08 |
snapshot · 2026-09-15
Failure clusters
-
observed PROJECT_TEST Evidence gap ×2 v5.2.2 → v5.3.1 executionContext=go · os=linux · runtime=go@1.26 jwt.ClaimsValidatorEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-09-08 · Last seen: 2026-09-08Diagnostic re-verification candidate