Behavioural Process Intelligence · Public Mirror
Node.js
What we read from 297 public GitHub events across the last 2 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Node.js · May 9, 2026
5 PRs merged with no independent review.
5 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.
nodejs/undici#5234·nodejs/node#62812·nodejs/node#63157·nodejs/node#63132·nodejs/node#63152
nodejs-github-bot authored 6/6 commits in nodejs/node. 100% concentration in this window. If nodejs-github-bot stops, nodejs/node stalls.
41% of writing this window was automated. github-actions[bot] accounts for 17 of 18 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
nodejs/node carried 74% of activity. 219 of 297 events in the last 2 weeks. Next: nodejs/jenkins-alerts (35).
8 issues opened, 84 issue comments. Issue traffic is 2.1× the code traffic this window — consumer-facing org or triage burst.
FIG 2 · Activity stats
FIG 3 · Repos by activity
- nodejs/node219 events · 6 commits · 5/8 PRs
- nodejs/jenkins-alerts35 events · 14 commits · 0/0 PRs
- nodejs/undici16 events · 6 commits · 2/0 PRs
- nodejs/docker-node14 events · 1 commit · 1/0 PRs
- nodejs/build4 events · 0 commits · 0/0 PRs
- nodejs/reliability2 events · 1 commit · 0/0 PRs
FIG 4 · Contributors by activity
- @nodejs-github-bot72 events · 30% share
- @aduh9526 events · 11% share
- @jasnell20 events · 8% share
- @mcollina12 events · 5% share
- @joyeecheung11 events · 5% share
- @panva11 events · 5% 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/nodejs)