Behavioural Process Intelligence · Public Mirror
Supabase
What we read from 299 public GitHub events across the last day. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Supabase · May 8, 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#45650·supabase/supabase#45696·supabase/wrappers#600
3 releases shipped without release notes. Examples: supabase/postgres 17.6.0.079-orioledb-pgbackrest-rc1, supabase/postgres 17.6.1.122-pgbackrest-rc1, supabase/postgres 15.14.1.122-pgbackrest-rc1. Short or empty release bodies — what did this ship and why?
supabase/postgres 17.6.0.079-orioledb-pgbackrest-rc1·supabase/postgres 17.6.1.122-pgbackrest-rc1·supabase/postgres 15.14.1.122-pgbackrest-rc1
ferhatelmas authored 6/6 commits in supabase/storage. 100% concentration in this window. If ferhatelmas stops, supabase/storage stalls.
41% of writing this window was automated. supabase-supabase-autofixer[bot] accounts for 18 of 46 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
supabase/supabase-js shipped 6 releases. Tagged release activity is the cleanest public signal of shipping rhythm. 4 other repos also shipped.
supabase/supabase-js v2.105.4·supabase/supabase-js v2.105.4-canary.2·supabase/supabase-js v3.0.0-next.28·supabase/supabase-js v3.0.0-next.27
supabase/supabase carried 34% of activity. 102 of 299 events in the last day. Next: supabase/storage (58).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- supabase/supabase102 events · 24 commits · 6/3 PRs
- supabase/storage58 events · 15 commits · 4/5 PRs
- supabase/supabase-js50 events · 7 commits · 6/4 PRs
- supabase/phoenix28 events · 7 commits · 4/2 PRs
- supabase/server16 events · 5 commits · 0/0 PRs
- supabase/etl9 events · 4 commits · 0/2 PRs
FIG 4 · Contributors by activity
- @mandarini39 events · 13% share
- @dependabot[bot]31 events · 10% share
- @supabase-supabase-autofixer[bot]29 events · 10% share
- @github-actions[bot]21 events · 7% share
- @ferhatelmas18 events · 6% share
- @awaseem16 events · 5% 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.
[](https://www.assemblr.net/mirror/supabase)