Behavioural Process Intelligence · Public Mirror
Charm
What we read from 298 public GitHub events across the last 8 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Charm · May 9, 2026
2 PRs merged with no independent review.
2 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.
charmbracelet/crush shipped 2 releases. Tagged release activity is the cleanest public signal of shipping rhythm. 2 other repos also shipped.
charmbracelet/crush carried 52% of activity. 154 of 298 events in the last 8 weeks. Next: charmbracelet/bubbletea (25).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- charmbracelet/crush154 events · 18 commits · 8/9 PRs
- charmbracelet/bubbletea25 events · 0 commits · 0/0 PRs
- charmbracelet/glow16 events · 0 commits · 0/0 PRs
- charmbracelet/fantasy15 events · 4 commits · 2/1 PRs
- charmbracelet/vhs12 events · 0 commits · 0/0 PRs
- charmbracelet/x9 events · 0 commits · 0/1 PRs
FIG 4 · Contributors by activity
- @taciturnaxolotl68 events · 24% share
- @andreynering36 events · 13% share
- @charmcli22 events · 8% share
- @sven27188 events · 3% share
- @smeinecke4 events · 1% share
- @EtAorangE4 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/charmbracelet)