Behavioural Process Intelligence · Public Mirror
Vite
What we read from 297 public GitHub events across the last 4 days. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Vite · May 9, 2026
18 PRs merged with no independent review.
18 PRs merged with no independent review. Spans 4 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
vitejs/docs-es#1896·vitejs/vite-ecosystem-ci#461·vitejs/vite-ecosystem-ci#463·vitejs/vite-ecosystem-ci#457·vitejs/devtools#323
sapphi-red is carrying 41% of the human writing work. 29 of 70 commit + PR-open + PR-merge events from a single human contributor.
sapphi-red authored 14/14 commits in vitejs/vite-plugin-vue. 100% concentration in this window. If sapphi-red stops, vitejs/vite-plugin-vue stalls.
49% of writing this window was automated. renovate[bot] accounts for 64 of 66 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
11 PRs merged between 22:00 and 06:00 UTC. Spans 2 repos. Either an always-on global org or a deploy-late-night habit.
vitejs/vite-plugin-vue#755·vitejs/vite-plugin-vue#762·vitejs/vite-plugin-vue#757·vitejs/vite-plugin-vue#773
vitejs/devtools shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
vitejs/vite carried 27% of activity. 80 of 297 events in the last 4 days. Next: vitejs/devtools (61).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- vitejs/vite80 events · 4 commits · 4/2 PRs
- vitejs/devtools61 events · 16 commits · 6/5 PRs
- vitejs/vite-plugin-vue61 events · 26 commits · 9/3 PRs
- vitejs/docs-de50 events · 31 commits · 3/2 PRs
- vitejs/vite-ecosystem-ci15 events · 6 commits · 3/1 PRs
- vitejs/docs-es14 events · 4 commits · 1/3 PRs
FIG 4 · Contributors by activity
- @sapphi-red65 events · 32% share
- @antfu32 events · 16% share
- @rojadesign15 events · 7% share
- @webfansplz9 events · 4% share
- @mstelbrink4 events · 2% share
- @seal-devops3 events · 1% 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/vitejs)