Behavioural Process Intelligence · Public Mirror
Vue
What we read from 300 public GitHub events across the last 3 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Vue · May 9, 2026
5 PRs merged with no independent review.
5 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.
vuejs/devtools#1096·vuejs/core#14789·vuejs/docs#3379·vuejs/docs#3388·vuejs/language-tools#6038
edison1105 authored 7/7 commits in vuejs/core. 100% concentration in this window. If edison1105 stops, vuejs/core stalls.
41% of writing this window was automated. renovate[bot] accounts for 22 of 26 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
5 PRs merged between 22:00 and 06:00 UTC. Spans 2 repos. Either an always-on global org or a deploy-late-night habit.
vuejs/core#14790·vuejs/devtools#1094·vuejs/devtools#1091·vuejs/devtools#1096
vuejs/devtools shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm. 1 other repo also shipped.
vuejs/core carried 22% of activity. 67 of 300 events in the last 3 weeks. Next: vuejs/vue (39).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- vuejs/core67 events · 7 commits · 2/2 PRs
- vuejs/vue39 events · 0 commits · 0/0 PRs
- vuejs/language-tools34 events · 1 commit · 1/1 PRs
- vuejs/docs31 events · 3 commits · 2/1 PRs
- vuejs/devtools30 events · 11 commits · 3/0 PRs
- vuejs/vitepress16 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @edison110521 events · 9% share
- @KazariEX20 events · 8% share
- @webfansplz14 events · 6% share
- @brc-dd14 events · 6% share
- @posva7 events · 3% share
- @spaceemotion7 events · 3% 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/vuejs)