Behavioural Process Intelligence · Public Mirror
Tailwind Labs
What we read from 299 public GitHub events across the last 6 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Tailwind Labs · May 9, 2026
RobinMalfait is carrying 95% of the human writing work.
3 PRs merged with no independent review. Spans 2 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
tailwindlabs/tailwindcss.com#2486·tailwindlabs/tailwindcss#20021·tailwindlabs/tailwindcss#20019
RobinMalfait is carrying 95% of the human writing work. 69 of 73 commit + PR-open + PR-merge events concentrated on a single human contributor. Bus-factor risk visible from the public feed.
RobinMalfait authored 28/28 commits in tailwindlabs/tailwindcss. 100% concentration in this window. If RobinMalfait stops, tailwindlabs/tailwindcss stalls.
tailwindlabs/tailwindcss shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
tailwindlabs/tailwindcss carried 69% of activity. 205 of 299 events in the last 6 weeks. Next: tailwindlabs/tailwindcss.com (36).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- tailwindlabs/tailwindcss205 events · 28 commits · 7/9 PRs
- tailwindlabs/tailwindcss.com36 events · 15 commits · 1/5 PRs
- tailwindlabs/tailwindcss-intellisense30 events · 8 commits · 1/2 PRs
- tailwindlabs/heroicons10 events · 0 commits · 0/0 PRs
- tailwindlabs/headlessui6 events · 0 commits · 0/0 PRs
- tailwindlabs/tailwind-plus-issues3 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @RobinMalfait108 events · 45% share
- @Copilot5 events · 2% share
- @wongjn4 events · 2% share
- @tomazartack3 events · 1% share
- @sankalpmukim3 events · 1% share
- @petersuhm3 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/tailwindlabs)