Behavioural Process Intelligence · Public Mirror

Astro

the Astro framework — github.com/withastro

What we read from 299 public GitHub events across the last 1 week. Real attribution preserved — these events are already public.

FIG 1 · Lede

Mirror · Astro · 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.

withastro/flue#93

2 PR/issues reopened this window — work didn't stick. 2 PR reopens + 0 issue reopens. Either the original close was premature, or the fix didn't fix it.

withastro/astro#16655·withastro/astro#16655

FredKSchott authored 6/6 commits in withastro/flue. 100% concentration in this window. If FredKSchott stops, withastro/flue stalls.

withastro/flue·@FredKSchott

2 PRs merged between 22:00 and 06:00 UTC. Spans 2 repos. Either an always-on global org or a deploy-late-night habit.

withastro/flue#93·withastro/starlight#3889

2 PRs merged on a weekend. Across 2 repos. Could be on-call work, could be habit drift.

withastro/flue#93·withastro/starlight#3889

withastro/starlight shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.

withastro/starlight @astrojs/starlight@0.39.2

withastro/flue carried 39% of activity. 117 of 299 events in the last 1 week. Next: withastro/astro (87).

withastro/flue

FIG 2 · Activity stats

Repos13

Contributors154

PRs opened19

PRs merged8

Commits28

Releases1

Reviews18

Issues opened2

FIG 3 · Repos by activity

withastro/flue117 events · 6 commits · 1/3 PRs
withastro/astro87 events · 14 commits · 1/4 PRs
withastro/starlight41 events · 3 commits · 3/4 PRs
withastro/docs39 events · 4 commits · 3/5 PRs
withastro/astro.build6 events · 0 commits · 0/2 PRs
withastro/automation2 events · 0 commits · 0/1 PRs

FIG 4 · Contributors by activity

@matthewp25 events · 11% share
@FredKSchott21 events · 9% share
@ArmandPhilippot12 events · 5% share
@delucis8 events · 3% share
@jsparkdev7 events · 3% share
@tats-u5 events · 2% 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.

[![Behavioural Mirror](https://www.assemblr.net/mirror/withastro/badge.svg)](https://www.assemblr.net/mirror/withastro)