Behavioural Process Intelligence · Public Mirror
Svelte
What we read from 299 public GitHub events across the last 2 days. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Svelte · May 9, 2026
9 PRs merged with no independent review.
9 PRs merged with no independent review. Spans 3 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
sveltejs/cli#1086·sveltejs/cli#1087·sveltejs/cli#1080·sveltejs/cli#1081·sveltejs/cli#1082
jycouet authored 7/7 commits in sveltejs/cli. 100% concentration in this window. If jycouet stops, sveltejs/cli stalls.
43% of writing this window was automated. github-actions[bot] accounts for 32 of 43 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
sveltejs/cli shipped 2 releases. Tagged release activity is the cleanest public signal of shipping rhythm.
sveltejs/cli sv@0.15.3·sveltejs/cli @sveltejs/sv-utils@0.2.2
sveltejs/svelte carried 36% of activity. 108 of 299 events in the last 2 days. Next: sveltejs/cli (44).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- sveltejs/svelte108 events · 22 commits · 5/7 PRs
- sveltejs/cli44 events · 12 commits · 7/4 PRs
- sveltejs/svelte.dev43 events · 17 commits · 0/2 PRs
- sveltejs/kit36 events · 3 commits · 1/3 PRs
- sveltejs/language-tools23 events · 2 commits · 1/3 PRs
- sveltejs/vite-plugin-svelte20 events · 7 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @Rich-Harris33 events · 17% share
- @jycouet26 events · 14% share
- @dummdidumm25 events · 13% share
- @jasonlyu12314 events · 7% share
- @teemingc12 events · 6% share
- @repo10009 events · 5% 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/sveltejs)