Skip to content

P2.6: Fixtures — JWT crypto-trust scenarios #75

Description

@bjcorder

Parent tracker: #62
Spec: docs/superpowers/specs/2026-05-21-edge-case-hardening-design.md
Milestone: P2
Depends on: P2.1, P2.2, P2.3, P2.4, P2.5

Goal

Add representative fixtures for each new P2 check across jsonwebtoken, jose, and PyJWT.

Acceptance criteria

  • Fixtures under fixtures/generic-{js,ts,python}/jwt-crypto-trust-{alg-none,alg-confusion,jku,x5u,embedded-jwk,nbf,clock-skew,kid}/.
  • Positive (clean), negative (vulnerable), and false-positive variants where each applies.
  • Each fixture ships an expected.json covering artifacts, evidence, and findings.
  • All fixtures use obvious placeholder keys / tokens / strings only. No real credentials.

Files touched

  • fixtures/generic-{js,ts,python}/jwt-crypto-trust-*/*

Doc-update checklist

  • None for this issue. Doc updates land in P2.7.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions