Skip to content

fix: avoid misidentifying Clerk secrets as Stripe keys - #82

Merged
omerbek merged 2 commits into
mainfrom
fix/shared-stripe-clerk-key-label
Nov 10, 2026
Merged

omerbek merged 2 commits into
mainfrom
fix/shared-stripe-clerk-key-label

Conversation

@omerbek

@omerbek omerbek commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

Live secret keys with the shared sk_live_ prefix now report as “Secret key (Stripe or Clerk)”. Stripe rk_live_ restricted keys retain a provider-specific finding. Each token produces one finding, and publishable keys remain unreported. Both README provider lists now include Clerk.

Clerk and Stripe document the same sk_live_ prefix without a guaranteed distinguishing suffix. Existing suffix matching and live-key scope are preserved.

The Python test job uses Ubuntu 22.04 because Python 3.9 setup fails on the current Ubuntu 26.04 runner. The existing Python 3.9/3.13 matrix is preserved.

References

Validation

  • python3 -m unittest discover — 115 tests passed locally
  • python3 repodx.py . — 100/100 locally
  • Regression coverage checks varying suffix lengths, restricted keys, and publishable keys.

Fixes #71

@omerbek
omerbek merged commit e845025 into main Nov 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Report Clerk secret keys as Clerk, not as Stripe

1 participant