Behavioural Process Intelligence · Public Mirror
NestJS
What we read from 300 public GitHub events across the last day. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · NestJS · May 9, 2026
41 PRs merged with no independent review.
41 PRs merged with no independent review. Spans 20 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
nestjs/schematics#2346·nestjs/typeorm#2597·nestjs/mongoose#2802·nestjs/axios#1694·nestjs/event-emitter#1724
98% of writing this window was automated. renovate[bot] accounts for 165 of 170 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
3 PRs merged between 22:00 and 06:00 UTC. Spans 3 repos. Either an always-on global org or a deploy-late-night habit.
nestjs/schematics#2346·nestjs/typeorm#2597·nestjs/mongoose#2802
3 PRs merged on a weekend. Across 3 repos. Could be on-call work, could be habit drift.
nestjs/schematics#2346·nestjs/typeorm#2597·nestjs/mongoose#2802
nestjs/nest carried 10% of activity. 31 of 300 events in the last day. Next: nestjs/schematics (19).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- nestjs/nest31 events · 0 commits · 0/6 PRs
- nestjs/schematics19 events · 9 commits · 3/2 PRs
- nestjs/typeorm18 events · 6 commits · 3/3 PRs
- nestjs/mongoose16 events · 4 commits · 3/3 PRs
- nestjs/graphql16 events · 5 commits · 2/2 PRs
- nestjs/throttler15 events · 7 commits · 2/2 PRs
FIG 4 · Contributors by activity
- @coveralls6 events · 26% share
- @pandaPowder3 events · 13% share
- @tiagotcunha2 events · 9% share
- @abstractorDev1 event · 4% share
- @ManlyMark1 event · 4% share
- @postigodev1 event · 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/nestjs)