Behavioural Process Intelligence · Public Mirror
HashiCorp
What we read from 300 public GitHub events across the last 9 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · HashiCorp · 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.
hashicorp/nomad-driver-podman shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm. 2 other repos also shipped.
hashicorp/terraform-provider-google carried 34% of activity. 102 of 300 events in the last 9 weeks. Next: hashicorp/terraform-provider-aws (73).
7 issues opened, 168 issue comments. Issue traffic is 9.2× the code traffic this window — consumer-facing org or triage burst.
FIG 2 · Activity stats
FIG 3 · Repos by activity
- hashicorp/terraform-provider-google102 events · 0 commits · 0/1 PRs
- hashicorp/terraform-provider-aws73 events · 0 commits · 0/1 PRs
- hashicorp/terraform-provider-azurerm24 events · 0 commits · 0/0 PRs
- hashicorp/terraform20 events · 3 commits · 0/1 PRs
- hashicorp/nomad12 events · 0 commits · 0/0 PRs
- hashicorp/terraform-provider-google-beta8 events · 1 commit · 0/1 PRs
FIG 4 · Contributors by activity
- @jbbqqf16 events · 19% share
- @melinath6 events · 7% share
- @jbardin5 events · 6% share
- @schmichael5 events · 6% share
- @tejashwiniingalagi3 events · 4% share
- @gautambaghel3 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/hashicorp)