Behavioural Process Intelligence · Public Mirror

Deno

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

FIG 1 · Lede

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

denoland/deno#33914·denoland/deno#33909·denoland/rusty_v8#1975·denoland/deno#33360

bartlomieju is carrying 61% of the human writing work. 57 of 93 commit + PR-open + PR-merge events from a single human contributor.

@bartlomieju

denobot authored 15/15 commits in denoland/benchmark_data. 100% concentration in this window. If denobot stops, denoland/benchmark_data stalls.

denoland/benchmark_data·@denobot

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

denoland/deno#33930·denoland/deno#33929·denoland/deno#33912

denoland/deno carried 84% of activity. 251 of 299 events in the last 4 days. Next: denoland/benchmark_data (15).

denoland/deno

FIG 2 · Activity stats

Repos12

Contributors63

PRs opened23

PRs merged16

Commits57

Releases0

Reviews80

Issues opened8

FIG 3 · Repos by activity

denoland/deno251 events · 36 commits · 15/19 PRs
denoland/benchmark_data15 events · 15 commits · 0/0 PRs
denoland/rusty_v88 events · 2 commits · 1/1 PRs
denoland/std8 events · 0 commits · 0/2 PRs
denoland/fresh6 events · 0 commits · 0/0 PRs
denoland/v83 events · 3 commits · 0/0 PRs

FIG 4 · Contributors by activity

@bartlomieju95 events · 33% share
@fibibot87 events · 30% share
@denobot15 events · 5% share
@nathanwhit12 events · 4% share
@steve020815044 events · 1% share
@swcarter0074 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.

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