Potential fix for code scanning alert no. 22: Missing rate limiting #243
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.
Potential fix for https://github.com/unitaryfoundation/metriq-api/security/code-scanning/22
To address the issue, we will introduce rate limiting to the
accountController.new
route using theexpress-rate-limit
package. This middleware will restrict the number of requests a client can make to the endpoint within a specified time window. Specifically, we will:express-rate-limit
package.accountController.new
route.This fix ensures that the registration endpoint is protected against abuse while maintaining its functionality.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.