Behavioural Process Intelligence · Public Mirror

Supabase

What we read from 299 public GitHub events across the last 3 weeks. Real attribution preserved — these events are already public.

FIG 1 · Lede

Mirror · Supabase · May 9, 2026

3 PRs merged with no independent review.

3 PRs merged with no independent review. Spans 2 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.

supabase/supabase#45602·supabase/supabase#45716·supabase/postgres#2146

6 releases shipped without release notes. Examples: supabase/postgres 15.14.1.121-push-qlspsxywvzun, supabase/postgres 17.6.1.121-push-qlspsxywvzun, supabase/postgres 17.6.0.078-orioledb-push-qlspsxywvzun. Short or empty release bodies — what did this ship and why?

supabase/postgres 15.14.1.121-push-qlspsxywvzun·supabase/postgres 17.6.1.121-push-qlspsxywvzun·supabase/postgres 17.6.0.078-orioledb-push-qlspsxywvzun·supabase/postgres 17.6.0.078-orioledb-push-qlspsxywvzun-x86·supabase/postgres 15.14.1.121-push-qlspsxywvzun-x86

ferhatelmas authored 5/5 commits in supabase/storage. 100% concentration in this window. If ferhatelmas stops, supabase/storage stalls.

supabase/storage·@ferhatelmas

supabase/postgres shipped 6 releases. Tagged release activity is the cleanest public signal of shipping rhythm. 2 other repos also shipped.

supabase/supabase carried 47% of activity. 140 of 299 events in the last 3 weeks. Next: supabase/server (31).

supabase/supabase

FIG 2 · Activity stats

Repos18

Contributors87

PRs opened19

PRs merged10

Commits51

Releases9

Reviews24

Issues opened4

FIG 3 · Repos by activity

supabase/supabase140 events · 18 commits · 6/9 PRs
supabase/server31 events · 6 commits · 2/3 PRs
supabase/storage23 events · 5 commits · 0/2 PRs
supabase/supabase-swift18 events · 13 commits · 0/1 PRs
supabase/agent-skills13 events · 0 commits · 0/0 PRs
supabase/realtime13 events · 2 commits · 1/0 PRs

FIG 4 · Contributors by activity

@grdsdev19 events · 11% share
@awaseem18 events · 10% share
@charislam9 events · 5% share
@gregnr8 events · 5% share
@Copilot8 events · 5% share
@ferhatelmas7 events · 4% share

FIG 5 · Rituals we can't see from GitHub alone

Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:

Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream

This is what we'd see for your team.

Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.

Book a demo →

FIG 6 · Embed in your README

Paste this in your README. The badge updates daily and links back to this Mirror.

[![Behavioural Mirror](https://www.assemblr.net/mirror/supabase/badge.svg)](https://www.assemblr.net/mirror/supabase)