Behavioural Process Intelligence · Public Mirror

DeepSeek

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

FIG 1 · Lede

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

deepseek-ai/awesome-deepseek-agent#31·deepseek-ai/DeepGEMM#328

263 audience events, only 9 code events. 203 new stars + 29 new forks + comments, but only 9 commits/PRs in the last 3 weeks. Lots of people watching; few shipping.

deepseek-ai/awesome-deepseek-agent carried 32% of activity. 92 of 291 events in the last 3 weeks. Next: deepseek-ai/DeepSeek-V3 (57).

deepseek-ai/awesome-deepseek-agent

6 issues opened, 31 issue comments. Issue traffic is 4.1× the code traffic this window — consumer-facing org or triage burst.

FIG 2 · Activity stats

Repos23

Contributors226

PRs opened5

PRs merged2

Commits2

Releases0

Reviews2

Issues opened6

FIG 3 · Repos by activity

deepseek-ai/awesome-deepseek-agent92 events · 1 commit · 1/3 PRs
deepseek-ai/DeepSeek-V357 events · 0 commits · 0/1 PRs
deepseek-ai/awesome-deepseek-integration29 events · 0 commits · 0/0 PRs
deepseek-ai/DeepGEMM16 events · 1 commit · 1/0 PRs
deepseek-ai/DeepSeek-Coder15 events · 0 commits · 0/0 PRs
deepseek-ai/DeepSeek-R112 events · 0 commits · 0/0 PRs

FIG 4 · Contributors by activity

@leo-sai5 events · 2% share
@muhammadtarek984 events · 1% share
@wazituzi4 events · 1% share
@wangcan264 events · 1% share
@YajiegaoJay4 events · 1% share
@icophy3 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/deepseek-ai/badge.svg)](https://www.assemblr.net/mirror/deepseek-ai)