Repository navigation
fix(security): redact GatewayCredentials representations - #137
Conversation
|
Warning Review limit reached
Next review available in: 34 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Test-first security repair for #128
Protected main now includes #71, so the former provider-client writer dependency is satisfied. This bounded branch hardens only
GatewayCredentialsrepresentation confidentiality without changing credential resolution or transport semantics.Current RED head
c29cdc40139cea6d9c43a9e69bfb75e528e270b6adds a focused regression proving provider API-key sentinel material must not appear inrepr()orstr(), while preserving constructor access, equality behavior, class identity, and visible non-secret gateway URL. The production fix will follow on this same branch after the intended RED is observed.No serialization, encryption, persistence, provider protocol, workflow, schema, or release authority claim is made. Direct attribute access and caller-controlled serialization remain separate authority surfaces.
Refs #128.