Behavioural Process Intelligence · Public Mirror
Linear
What we read from 295 public GitHub events across the last 26 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Linear · May 9, 2026
4 PRs merged with no independent review.
4 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.
linear/linear#1132·linear/linear#1133·linear/linear-release#61·linear/linear-release#60
216 audience events, only 8 code events. 173 new stars + 27 new forks + comments, but only 8 commits/PRs in the last 26 weeks. Lots of people watching; few shipping.
linear/linear shipped 8 releases. Tagged release activity is the cleanest public signal of shipping rhythm. 2 other repos also shipped.
linear/linear @linear/sdk@84.0.0·linear/linear @linear/import@3.1.6·linear/linear @linear/sdk@83.0.0·linear/linear @linear/import@3.1.5
linear/linear carried 52% of activity. 154 of 295 events in the last 26 weeks. Next: linear/claude-managed-agents-demo (59).
10 issues opened, 16 issue comments. Issue traffic is 3.3× the code traffic this window — consumer-facing org or triage burst.
FIG 2 · Activity stats
FIG 3 · Repos by activity
- linear/linear154 events · 1 commit · 2/2 PRs
- linear/claude-managed-agents-demo59 events · 0 commits · 0/0 PRs
- linear/linear-release39 events · 0 commits · 2/1 PRs
- linear/linear-release-action23 events · 0 commits · 0/0 PRs
- linear/weather-bot7 events · 0 commits · 0/0 PRs
- linear/linear-solutions6 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @RomainCscn6 events · 3% share
- @sundaram20214 events · 2% share
- @eriknomitch4 events · 2% share
- @shannonwho4 events · 2% share
- @TomBombadil-heyho4 events · 2% share
- @itsmingjie3 events · 1% 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/linear)