Behavioural Process Intelligence · Public Mirror

React

What we read from 300 public GitHub events across the last 6 days. Real attribution preserved — these events are already public.

FIG 1 · Lede

Mirror · React · May 9, 2026

9 PRs merged with no independent review.

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

reactjs/react-tabs#614·reactjs/react-docgen#1092·reactjs/react-docgen#1091·reactjs/react-docgen#1090·reactjs/react-docgen#1078

react-translations-bot is carrying 53% of the human writing work. 30 of 57 commit + PR-open + PR-merge events from a single human contributor.

@react-translations-bot

danez authored 8/8 commits in reactjs/react-docgen. 100% concentration in this window. If danez stops, reactjs/react-docgen stalls.

reactjs/react-docgen·@danez

55% of writing this window was automated. renovate[bot] accounts for 62 of 70 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.

@renovate[bot]

reactjs/react-docgen carried 42% of activity. 125 of 300 events in the last 6 days. Next: reactjs/react-tabs (37).

reactjs/react-docgen

FIG 2 · Activity stats

Repos44

Contributors59

PRs opened16

PRs merged11

Commits100

Releases0

Reviews7

Issues opened3

FIG 3 · Repos by activity

reactjs/react-docgen125 events · 52 commits · 5/5 PRs
reactjs/react-tabs37 events · 13 commits · 1/1 PRs
reactjs/react.dev35 events · 0 commits · 0/4 PRs
reactjs/react-rails19 events · 0 commits · 0/3 PRs
reactjs/ko.react.dev11 events · 1 commit · 1/1 PRs
reactjs/cs.react.dev10 events · 4 commits · 3/0 PRs

FIG 4 · Contributors by activity

@react-translations-bot30 events · 24% share
@danez19 events · 15% share
@harshilparmar6 events · 5% share
@caiolucasbittencourt5 events · 4% share
@pchalupa5 events · 4% share
@goodsmell3 events · 2% 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/reactjs/badge.svg)](https://www.assemblr.net/mirror/reactjs)