Behavioural Process Intelligence · Public Mirror
Prisma
What we read from 278 public GitHub events across the last day. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Prisma · May 9, 2026
1 PR merged with no independent review.
1 PR merged with no independent review. Spans 1 repo. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
1 release shipped without release notes. Examples: prisma/language-tools insider/31.10.4. Short or empty release bodies — what did this ship and why?
prisma/language-tools shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
prisma/prisma-next carried 65% of activity. 182 of 278 events in the last day. Next: prisma/web (34).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- prisma/prisma-next182 events · 21 commits · 2/2 PRs
- prisma/web34 events · 15 commits · 0/1 PRs
- prisma/prisma-cli31 events · 3 commits · 0/1 PRs
- prisma/prisma17 events · 0 commits · 0/1 PRs
- prisma/language-tools7 events · 6 commits · 0/0 PRs
- prisma/prisma-examples5 events · 5 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @wmadden91 events · 54% share
- @jkomyno18 events · 11% share
- @aidankmcalister10 events · 6% share
- @SevInf7 events · 4% share
- @carlagn6 events · 4% share
- @kristof-siket6 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/prisma)