Fix: Rate limiting on the key-bundle fetch endpoint (Auto-Generated) - #430
Merged
codebestia merged 2 commits intoJul 30, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #331
This PR was generated by the DripTide AI coder and scoped strictly to issue #331.
Changes
Added an authenticated caller-and-target-device scoped express-rate-limit middleware to the key-bundle endpoint, allowing up to 10 requests per minute and returning the same 429 response format used by the authentication routes.
Verification
Passed automated self-review (lint + issue-coverage checks).
Linked with
Closes #331so the Drips Wave bot resolves the issue on merge.