Behavioural Process Intelligence · Public Mirror
shadcn/ui
What we read from 295 public GitHub events across the last 3 days. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · shadcn/ui · May 9, 2026
4 PRs merged with no independent review.
4 PRs merged with no independent review. Spans 1 repo. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
shadcn-ui/ui#10584·shadcn-ui/ui#10558·shadcn-ui/ui#10581·shadcn-ui/ui#10573
5 issues opened, only 1 closed. Net +4 this window. Triage backlog is growing — maintainer queue lengthening.
shadcn-ui/ui#10593·shadcn-ui/ui#10592·shadcn-ui/ui#10582·shadcn-ui/ui#10576·shadcn-ui/ui#10574
shadcn is carrying 45% of the human writing work. 10 of 22 commit + PR-open + PR-merge events from a single human contributor.
shadcn authored 6/6 commits in shadcn-ui/ui. 100% concentration in this window. If shadcn stops, shadcn-ui/ui stalls.
3 PRs merged between 22:00 and 06:00 UTC. Spans 1 repo. Either an always-on global org or a deploy-late-night habit.
shadcn-ui/ui carried 95% of activity. 281 of 295 events in the last 3 days. Next: shadcn-ui/taxonomy (12).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- shadcn-ui/ui281 events · 13 commits · 5/11 PRs
- shadcn-ui/taxonomy12 events · 0 commits · 0/0 PRs
- shadcn-ui/registry-template1 event · 0 commits · 0/0 PRs
- shadcn-ui/next-template-rtl1 event · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @shadcn18 events · 7% share
- @galoi5 events · 2% share
- @lunaxislu3 events · 1% share
- @kkzakaria2 events · 1% share
- @giriexplores2 events · 1% share
- @digitalsofterp2 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/shadcn-ui)