Issues

• webpki::aki::root-with-aki-* tests use invalid chains

  C2SP/x509-limbo#641 · Filter by author randombit opened on Jul 16, 2026

• Broken RFC5280 test cases due to incorrect chain

  C2SP/x509-limbo#634 · Filter by author ralphje opened on Jul 5, 2026
  7

• Link to search for root-program trusted certificates violating each testcase

  C2SP/x509-limbo#622 · Filter by author rolandshoemaker opened on Jun 1, 2026

• rfc5280::nc::permitted-dns-match-noncritical is unlikely to ever be considered invalid

  C2SP/x509-limbo#602 · Filter by author nbastin opened on Apr 22, 2026

• More CVE testcases

  C2SP/x509-limbo#593 · Filter by author woodruffw opened on Apr 12, 2026

• pathlen::intermediate-pathlen-may-increase is incorrect

  C2SP/x509-limbo#581 · Filter by author nbastin opened on Apr 4, 2026
  5

• Add tests cases for CVE-2026-27137 and CVE-2026-27138

  help wanted
  C2SP/x509-limbo#565 · Filter by author alex opened on Mar 6, 2026

• CABF test: certs with different subject/issuer encodings should be rejected

  C2SP/x509-limbo#563 · Filter by author woodruffw opened on Mar 2, 2026

• PRs from third-party forks trigger workflow errors

  C2SP/x509-limbo#539 · Filter by author jvdprng opened on Jan 2, 2026

• Provide test cases as PKCS #7 alongside JSON

  good first issuehelp wanted
  C2SP/x509-limbo#513 · Filter by author fencepost-error opened on Nov 13, 2025
  4

• Regression detection follow-ons

  C2SP/x509-limbo#202 · Filter by author woodruffw opened on Feb 14, 2024
  2

  

• RFE - Expected path in limbo.json

  C2SP/x509-limbo#195 · Filter by author cipherboy opened on Feb 10, 2024
  1

• Do a proper release + embed limbo.json as a release asset

  C2SP/x509-limbo#188 · Filter by author woodruffw opened on Feb 1, 2024

• Additional testcases

  component:tests 🧪
  C2SP/x509-limbo#174 · Filter by author woodruffw opened on Jan 17, 2024
  3

• Additional harness ideas

  component:tests 🧪enhancement ✨
  C2SP/x509-limbo#168 · Filter by author woodruffw opened on Jan 12, 2024
  2

• Communicate "why it matters" on each testcase

  C2SP/x509-limbo#161 · Filter by author woodruffw opened on Jan 3, 2024
  2

  

• Track and report harness-found bugs to upstream implementations

  C2SP/x509-limbo#155 · Filter by author woodruffw opened on Dec 26, 2023
  1

  

• CI: Enforce that limbo.json is up-to-date

  component:CI/CD 🤖
  C2SP/x509-limbo#150 · Filter by author woodruffw opened on Dec 21, 2023
  2

  

• Render the JSON schema on the site

  enhancement ✨
  C2SP/x509-limbo#112 · Filter by author woodruffw opened on Nov 29, 2023
  2

  

• Stabilize identifiers

  C2SP/x509-limbo#87 · Filter by author woodruffw opened on Nov 15, 2023 · MVP

• Consider modelling failure reasons into Limbo spec

  enhancement ✨
  C2SP/x509-limbo#43 · Filter by author tetsuo-cpp opened on Oct 18, 2023
  4

• Support key_usage in the harnesses

  enhancement ✨
  C2SP/x509-limbo#36 · Filter by author tetsuo-cpp opened on Sep 4, 2023

• Idea: add a limbo subcommand that generates a reasonably formatted GitHub issue

  enhancement ✨
  C2SP/x509-limbo#12 · Filter by author woodruffw opened on Jul 1, 2023
  2

• Determine a key reuse/output regeneration policy

  C2SP/x509-limbo#8 · Filter by author woodruffw opened on Jun 20, 2023
  4