Behavioural Process Intelligence · Public Mirror
Pulumi
What we read from 300 public GitHub events across the last 4 days. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Pulumi · May 9, 2026
4 PRs merged with no independent review.
4 PRs merged with no independent review. Spans 4 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
pulumi/pulumi-aiven#1168·pulumi/pulumi-snowflake#1175·pulumi/pulumi-kubernetes-operator#1202·pulumi/pulumi-azure-native#4712
100% of writing this window was automated. pulumi-bot accounts for 69 of 132 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
11 PRs merged between 22:00 and 06:00 UTC. Spans 11 repos. Either an always-on global org or a deploy-late-night habit.
pulumi/pulumi-aiven#1168·pulumi/registry#10956·pulumi/pulumi-kubernetes-cert-manager#1005·pulumi/pulumi-snowflake#1175
11 PRs merged on a weekend. Across 11 repos. Could be on-call work, could be habit drift.
pulumi/pulumi-aiven#1168·pulumi/registry#10956·pulumi/pulumi-kubernetes-cert-manager#1005·pulumi/pulumi-snowflake#1175
pulumi/pulumi-snowflake shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
pulumi/pulumi-snowflake carried 21% of activity. 63 of 300 events in the last 4 days. Next: pulumi/pulumi-eks (52).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- pulumi/pulumi-snowflake63 events · 1 commit · 1/1 PRs
- pulumi/pulumi-eks52 events · 52 commits · 0/0 PRs
- pulumi/pulumi-kubernetes-cert-manager18 events · 2 commits · 1/2 PRs
- pulumi/registry14 events · 1 commit · 1/2 PRs
- pulumi/pulumi-aws-apigateway12 events · 2 commits · 1/1 PRs
- pulumi/pulumi-kubernetes-ingress-nginx12 events · 1 commit · 1/1 PRs
FIG 4 · Contributors by activity
- @WolffM1 event · 100% 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/pulumi)