• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / auth / 16504003623
71%
master: 69%

Build:
Build:
LAST BUILD BRANCH: cs/error-code-metrics
DEFAULT BRANCH: master
Ran 24 Jul 2025 05:50PM UTC
Jobs 1
Files 145
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

24 Jul 2025 05:43PM UTC coverage: 70.481% (-0.01%) from 70.495%
16504003623

Pull #2090

github

Chris Stockton
chore: make it more clear which rate limiters use the OTP limit

In the supabase dashboard the rate limits are declared as:

  - `RATE_LIMIT_OTP` Rate limit for sign ups and sign ins
      Number of sign up and sign-in requests that can be
      made in a 5 minute interval per IP address

  - `RATE_LIMIT_VERIFY` Rate limit for token verifications
      Number of OTP/Magic link verifications that can be
      made in a 5 minute interval per IP address

This does not exactly translate to the rate limit usage in the
auth server. But it isn't something we may change, so for now
I'm just making this usage more clear and documenting it.
Pull Request #2090: chore: make it more clear which rate limiters use the OTP limit

2 of 2 new or added lines in 1 file covered. (100.0%)

11814 of 16762 relevant lines covered (70.48%)

70.43 hits per line

Jobs
ID Job ID Ran Files Coverage
1 16504003623.1 24 Jul 2025 05:50PM UTC 145
70.48
GitHub Action Run
Source Files on build 16504003623
  • Tree
  • List 145
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #2090
  • PR Base - master (#16492281791)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc