repowiserepowise
Sign in
2233admin/pi-peer
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowise2233admin/pi-peer

Commits

Every commit scored for change-risk against this repo's own history, so 'elevated' means elevated here rather than on some global curve.

Needs review

3of 8 scored

3 commits sit in this repo's top risk tercile, which is 38% of the 8scored. The cut is drawn against this codebase's own history rather than a global curve, so a quiet repo still fills its top band, and here it starts at 9.3 out of 10. What pushes a commit up is size and spread together: a large change confined to one area scores below a smaller one scattered across a dozen files.

Fix commits00%Commits whose subject reads as a bug fix rather than new work.Change diffusion1.69bitsShannon entropy of a commit's churn across its files. Zero is a single file, and every extra bit is a doubling of how widely the change spread.Review threshold9.3out of 10Score a commit has to clear to land in this repo's top tercile.

How the work changed shape

Commit categories over time, read off the subject line. Fixes carry the accent because that is the series this chart exists to show.

How this repo's commit mix shifts over time.

Deps13%
Other88%

Review-priority queue

Ranked by change-risk, highest first. Priority is a tercile of this repo's own distribution, so a quiet repo still fills its top band.

Commit review-priority queue
#CommitAuthorWhenLinesRiskTop driver
1
7e1bf270pi-peer: pi sessions find and message each other through a shared mailbox
Michael Livshits
5d ago+3.3K -0
94%Elevated
more lines added than baseline
2
5738b68eRemote peer messaging over a shared Redis, behind a setting
Shani Kaneti
4d ago+1.9K -220
81%Elevated
more lines added than baseline
3
349af17bInteractive configuration: /peer-remote, persisted to pi-peer.json
Shani Kaneti
4d ago+554 -39
69%Elevated
more lines added than baseline
4
4722adfbQueued remote sends no longer leak their ack subscription, and the edge cases are pinned
Michael Livshits
3d ago+270 -6
56%Typical
more lines added than baseline
5
896a7595Survive the handshake: connect before commanding, subscribe after ready
Shani Kaneti
4d ago+92 -25
44%Typical
more lines added than baseline
6
ad7a795aShip ioredis as a regular dependency
Shani Kaneti
4d ago+21 -5
31%Below typical
more lines added than baseline
7
b4803a74One settings resolution path, not two
Michael Livshits
3d ago+4 -49
19%Below typical
fewer lines added than baseline
8
5e8fcb20v0.2.0
Michael Livshits
3d ago+1 -1
6%Below typical
fewer lines added than baseline
  • 7e1bf270pi-peer: pi sessions find and message each other through a shared mailbox
    Author
    Michael Livshits
    When
    5d ago
    Lines
    +3.3K -0
    Risk
    94%Elevated
  • 5738b68eRemote peer messaging over a shared Redis, behind a setting
    Author
    Shani Kaneti
    When
    4d ago
    Lines
    +1.9K -220
    Risk
    81%Elevated
  • 349af17bInteractive configuration: /peer-remote, persisted to pi-peer.json
    Author
    Shani Kaneti
    When
    4d ago
    Lines
    +554 -39
    Risk
    69%Elevated
  • 4722adfbQueued remote sends no longer leak their ack subscription, and the edge cases are pinned
    Author
    Michael Livshits
    When
    3d ago
    Lines
    +270 -6
    Risk
    56%Typical
  • 896a7595Survive the handshake: connect before commanding, subscribe after ready
    Author
    Shani Kaneti
    When
    4d ago
    Lines
    +92 -25
    Risk
    44%Typical
  • ad7a795aShip ioredis as a regular dependency
    Author
    Shani Kaneti
    When
    4d ago
    Lines
    +21 -5
    Risk
    31%Below typical
  • b4803a74One settings resolution path, not two
    Author
    Michael Livshits
    When
    3d ago
    Lines
    +4 -49
    Risk
    19%Below typical
  • 5e8fcb20v0.2.0
    Author
    Michael Livshits
    When
    3d ago
    Lines
    +1 -1
    Risk
    6%Below typical
Showing 8 of 8 commits

How the score behaves here

Change risk →

Two views of the same model: where the cuts fall, and what commit shape lands you above them.

Score distribution

Every scored commit, binned on the raw 0 to 10 score rather than the percentile. Percentile ranks are uniform by construction, so that axis has no shape to draw. The dashed lines are the tercile cuts behind each row's priority pill.

02typical ↑↑ elevated0.05.010.0Change-risk score →
Below typical
Typical
Elevated

Size against diffusion

The 8 most recent commits, on their own recency sample rather than the feed above: that defaults to risk-sorted, so reusing it would plot only the top tercile and call it the spread. Big and scattered is what the model penalises. Click a dot to open it.

1101001,000Lines changed (log) →0.04.0Diffusion →
Below typical3
Typical2
Elevated3

Commit history for 2233admin/pi-peer

2233admin/pi-peer has 9 commits in its history from 3 contributors, the first of them Aug 7, 2026. In the last 90 days 19 files were touched, 36 times in total, most often index.ts. Every commit is scored for change risk from its size, spread and the history of the files it touches.