supabase/realtime - Open Source PR Review Scorecard

Broadcast, Presence, and Postgres Changes via WebSockets

C-Rank Grade: A (Welcoming) - 64/100

External PR Merge Rate: 83%

Response Time: -

First Timer Success: 33%

Frequently Asked Questions

Is supabase/realtime welcoming to first-time open-source contributors?

supabase/realtime has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in supabase/realtime respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.3 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.3 places supabase/realtime in the A tier.

What is the external contributor pull request merge rate for supabase/realtime?

The external contributor pull request merge rate for supabase/realtime is 83.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in supabase/realtime?

supabase/realtime does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

supabase
supabase/realtimeA•Welcoming7.6k
GitHub
Back to Explorer
supabase

supabase/realtime

7,649
Active (30d)A•Welcoming(64/100)Elixir

Broadcast, Presence, and Postgres Changes via WebSockets

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.9/10
Patience Score
8.4/10
Nitpick Rate
20%

Highly welcoming maintainers in supabase/realtime. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
83.5%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
33.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
13 core
Highly collaborative maintainer core
Diagnostic Health HUD
83.5%
Merge Gauge
33.3%
1st-Timer
Community Vibe43/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for supabase/realtime
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/supabase/realtime)](https://getmerged.abhishekco.de/supabase/realtime?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Problem With config.broadcast.ack: true, a client that sends a broadcast on a private channel waits for the server to reply. When an RLS write policy denies the broadcast, or the broadcast fails on the server, Realtime never replies. The push times out, and supabase-js resolves send() with 'timed out' instead of 'error': https://github.com/supabase/supabase-js/blob/54c225dacb1fc5f5a0a97c93908a46b7e8f5c9cc/packages/core/realtime-js/src/RealtimeChannel.ts#L1119-L1125 A denied write looks like a network problem, so people debug latency instead of their policies. BroadcastHandler.handle/3 returns {:noreply, socket} regardless of ack_broadcast when the write policy denies the message and in every error clause: realtime/lib/realtime_web/channels/realtime_channel/broadcast_handler.ex Lines 80 to 104 in a3591b3 {:ok, policies} -> {:noreply, assign(socket, :po

📅 Opened Sep 23, 2026💬 1 comment
Quality: 90/100Contribute

Problem Subscriptions.delete_all/1 runs delete from realtime.subscription; without checking that the table exists: realtime/lib/extensions/postgres_cdc_rls/subscriptions.ex Lines 163 to 173 in a85489e @spec delete_all(conn()) :: :ok def delete_all(conn) do Logger.debug("Delete all subscriptions") case query(conn, "delete from realtime.subscription;", []) do {:ok, _} -> :ok {:error, reason} -> log_error("SubscriptionDeletionFailed", reason) end catch :exit, reason -> log_error("SubscriptionDeletionFailed", {

📅 Opened Sep 17, 2026💬 1 comment
Quality: 90/100Contribute
Looking for more Elixir beginner tasks?Explore Elixir GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for supabase/realtime

When evaluating whether to contribute to supabase/realtime, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of supabase/realtime acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to supabase/realtime

01

Is supabase/realtime welcoming to first-time open-source contributors?

supabase/realtime has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 64.3 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.3 places supabase/realtime in the Welcoming tier.

04

What is the external contributor pull request merge rate for supabase/realtime?

The external pull request merge rate is 83.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in supabase/realtime?

supabase/realtime does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for supabase/realtime are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.