🔒 fix(security): remove in-memory rate limiting fallback

[is0692vs]

Removes the in-memory rate limiting fallback to enforce distributed rate limiting across serverless instances.

---

PR created automatically by Jules for task 9954268514339663405 started by @is0692vs

Greptile Summary

This PR makes rate limiting require Redis outside tests. The main changes are:

• Removes the production in-memory rate-limit fallback.
• Keeps a test-only map fallback for route tests.
• Updates rate-limit tests to expect missing Redis config to throw.
• Updates card and OG route tests to mock rate-limit failures directly.

Confidence Score: 4/5

Redis misconfiguration can make the changed API routes return uncaught 500s.

• The security direction is sound: production no longer falls back to per-instance memory.
• The new throw is reachable before route-level error handling.
• The card and OG endpoints need a controlled response path for missing Redis config.

src/lib/rateLimit.ts and the card/OG route callers

Security Review

The change removes the weak per-instance fallback in production-like environments. The remaining concern is that missing Redis config now becomes an uncaught route error instead of a controlled failure response.

Important Files Changed

Filename	Overview
src/lib/rateLimit.ts	Redis is now required outside tests, with a test-only in-memory fallback kept behind environment checks.
src/lib/tests/rateLimit.test.ts	The fallback tests were replaced with a missing-configuration error test.
src/app/api/card/[username]/route.test.ts	The card route rate-limit test now spies on RateLimiter.check instead of filling the bucket.
src/app/api/og/[username]/route.test.ts	The OG route test now forces the final rate-limit failure with a prototype spy.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
src/lib/rateLimit.ts:25
**Redis Misconfiguration Returns 500**

When Upstash env vars are missing outside tests, this throw happens before the card and OG routes enter their existing error handling. A preview, staging, or local production build with missing Redis config will return uncaught 500s for every `/api/card/[username]` and `/api/og/[username]` request instead of a controlled response.

_{Reviews (1): Last reviewed commit: "🔒 fix(security): remove in-memory rate ..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ignored		Jul 17, 2026 6:46am

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

@is0692vs, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: deb2a764-4d5e-4987-8ed1-4babc4a318b4

📥 Commits

Reviewing files that changed from the base of the PR and between 0a9a1e0 and 3c095ee.

📒 Files selected for processing (4)

• src/app/api/card/[username]/route.test.ts
• src/app/api/og/[username]/route.test.ts
• src/lib/__tests__/rateLimit.test.ts
• src/lib/rateLimit.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-rate-limit-fallback-9954268514339663405

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

❌ Patch coverage is 70.00000% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/lib/rateLimit.ts	70.00%	3 Missing and 3 partials ⚠️

📢 Thoughts on this report? Let us know!

[greptile-apps]

Redis Misconfiguration Returns 500

When Upstash env vars are missing outside tests, this throw happens before the card and OG routes enter their existing error handling. A preview, staging, or local production build with missing Redis config will return uncaught 500s for every /api/card/[username] and /api/og/[username] request instead of a controlled response.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/lib/rateLimit.ts
Line: 25

Comment:
**Redis Misconfiguration Returns 500**

When Upstash env vars are missing outside tests, this throw happens before the card and OG routes enter their existing error handling. A preview, staging, or local production build with missing Redis config will return uncaught 500s for every `/api/card/[username]` and `/api/og/[username]` request instead of a controlled response.

How can I resolve this? If you propose a fix, please make it concise.

[is0692vs]

Closing because this Jules-managed branch cannot maintain a stable review-loop head: after the target branch is incorporated or a review fix is pushed, the bot appends the original generated change again. The current head is therefore not reliably the commit that passed target-fresh CI and review.