Behavioural Process Intelligence · Public Mirror

SolidJS

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

FIG 1 · Lede

Mirror · SolidJS · May 9, 2026

2 PRs merged with no independent review.

2 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.

solidjs/solid-start#2099·solidjs/solid-docs#1497

ryansolid authored 8/8 commits in solidjs/solid. 100% concentration in this window. If ryansolid stops, solidjs/solid stalls.

solidjs/solid·@ryansolid

69% of writing this window was automated. renovate[bot] accounts for 34 of 77 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.

@renovate[bot]

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

solidjs/solid-docs#1468·solidjs/solid-start#2099·solidjs/solid-start#2129·solidjs/solid-start#2132

solidjs/solid-docs carried 56% of activity. 168 of 299 events in the last 24 weeks. Next: solidjs/solid-start (57).

solidjs/solid-docs

FIG 2 · Activity stats

Repos22

Contributors62

PRs opened10

PRs merged9

Commits92

Releases0

Reviews24

Issues opened2

FIG 3 · Repos by activity

solidjs/solid-docs168 events · 71 commits · 5/7 PRs
solidjs/solid-start57 events · 13 commits · 4/1 PRs
solidjs/solid49 events · 8 commits · 0/1 PRs
solidjs/vite-plugin-solid3 events · 0 commits · 0/0 PRs
solidjs/solidhack3 events · 0 commits · 0/0 PRs
solidjs/solid-router2 events · 0 commits · 0/0 PRs

FIG 4 · Contributors by activity

@brenelz46 events · 26% share
@LadyBluenotes30 events · 17% share
@ryansolid18 events · 10% share
@aiminnovations15 events · 9% share
@lxsmnsyc5 events · 3% share
@katywings3 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/solidjs/badge.svg)](https://www.assemblr.net/mirror/solidjs)