Behavioural Process Intelligence · Public Mirror
Vercel
What we read from 297 public GitHub events across the last 2 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Vercel · May 8, 2026
18 PRs merged with no independent review.
18 PRs merged with no independent review. Spans 5 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
vercel/turborepo#12765·vercel/turborepo#12764·vercel/next.js#93612·vercel/sdk#290·vercel/sandbox#158
4 PR/issues reopened this window — work didn't stick. 4 PR reopens + 0 issue reopens. Either the original close was premature, or the fix didn't fix it.
vercel/ai#15114·vercel/ai#15114·vercel/ai#15114·vercel/ai#15114
vercel/turborepo shipped 3 releases. Tagged release activity is the cleanest public signal of shipping rhythm. 2 other repos also shipped.
vercel/turborepo v2.9.11-canary.5·vercel/turborepo v2.9.11-canary.4·vercel/turborepo v2.9.11-canary.3
vercel/next.js carried 38% of activity. 112 of 297 events in the last 2 weeks. Next: vercel/turborepo (58).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- vercel/next.js112 events · 3 commits · 3/10 PRs
- vercel/turborepo58 events · 6 commits · 11/10 PRs
- vercel/ai46 events · 1 commits · 4/7 PRs
- vercel/vercel29 events · 10 commits · 0/2 PRs
- vercel/sdk18 events · 3 commits · 3/3 PRs
- vercel/chat10 events · 0 commits · 0/2 PRs
FIG 4 · Contributors by activity
- @github-actions[bot]71 events · 24% share
- @aurorascharff35 events · 12% share
- @anthonyshew30 events · 10% share
- @vercel[bot]21 events · 7% share
- @lgrammel16 events · 5% share
- @feedthejim12 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.
[](https://www.assemblr.net/mirror/vercel)