Behavioural Process Intelligence · Public Mirror
Bun
the Bun runtime — github.com/oven-sh
What we read from 299 public GitHub events across the last day. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Bun · May 9, 2026
Jarred-Sumner is carrying 97% of the human writing work.
5 issues opened, only 0 closed. Net +5 this window. Triage backlog is growing — maintainer queue lengthening.
oven-sh/bun#30421·oven-sh/bun#30420·oven-sh/bun#30418·oven-sh/bun#30417·oven-sh/bun#30415
Jarred-Sumner is carrying 97% of the human writing work. 33 of 34 commit + PR-open + PR-merge events concentrated on a single human contributor. Bus-factor risk visible from the public feed.
Jarred-Sumner authored 33/34 commits in oven-sh/bun. 97% concentration in this window. If Jarred-Sumner stops, oven-sh/bun stalls.
54% of writing this window was automated. robobun accounts for 28 of 40 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
oven-sh/bun carried 98% of activity. 293 of 299 events in the last day. Next: oven-sh/homebrew-bun (1).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- oven-sh/bun293 events · 70 commits · 0/4 PRs
- oven-sh/homebrew-bun1 event · 0 commits · 0/0 PRs
- oven-sh/libuv1 event · 0 commits · 0/0 PRs
- oven-sh/zig1 event · 0 commits · 0/0 PRs
- oven-sh/mimalloc1 event · 0 commits · 0/0 PRs
- oven-sh/awesome-bun1 event · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @Jarred-Sumner35 events · 47% share
- @cirospaciari6 events · 8% share
- @ehanc695 events · 7% share
- @apacheli4 events · 5% share
- @xronocode3 events · 4% share
- @VenkatKwest3 events · 4% 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/oven-sh)