ryanportfolio/ryanportfolio

78 Strong

Commit: 332bbc418b1f908c7f63be07e0309f245e2812a6
Collected: 2026-07-18T18:47:29.588Z
Sample: 26 commits · 10 merged PRs
Publication: Requires prior owner approval: rule

Dimensions

Dimension	Score	Basis
Agent attribution & provenance Can every commit be traced to who or what made it (a linked account, a bot identity, or a co-author trailer)?	100	26/26 commits have clear provenance (linked account, bot identity, or co-author trailer). Agent-involved share is reported as context, not judged.
Recorded review coverage Of the merged pull requests, how many carry a recorded review by anyone other than the author?	0	0/10 merged PRs received at least one review not authored by the PR author.
Recorded review catch rate When a recorded review happened, did it change anything (new commits after the review, before the merge)?	could not verify	Could not verify: no reviewed PRs in sample.
Human merge gate Are merges performed by people, or does automation merge by itself?	100	10/10 sampled merges were performed by a non-bot account.
CI test/eval gate Do automated tests exist, and did pull requests actually pass them before merging?	100	3 workflow file(s) present (40pts). 100% of sampled merged PRs had all check runs passing at head (up to 60pts).
Batch size Are changes small, reviewable chunks, or thousand-line dumps?	85	Median merged-PR diff size is 286.5 lines (additions+deletions). Small batches score higher.
Lead time (first commit → merge) How long does work take from first commit to being merged?	100	Median lead time from first PR commit to merge is 0.4h.
Plan-before-code evidence Do pull requests link to an issue or plan that existed before the code?	100	10/10 merged PRs reference a linked issue or plan document in the PR body.
Audit-trail completeness Could a stranger reconstruct why each change happened (real descriptions, recorded reviews, recorded checks)?	66.7	Mean of: substantive PR description ≥120 chars (10/10), review recorded (0/10), CI checks recorded (10/10).

Could not verify

Excluded from the overall score rather than guessed: Recorded review catch rate.

What this score means

S-1

Process discipline, not code quality

This score measures process discipline, not code quality. The tool never reads the code. It reads only GitHub metadata: commits, pull requests, reviews, check runs, and merge events. It scores only what is recorded on GitHub; discipline that leaves no artifact there earns nothing.

S-2

One question

It answers one question: when AI agents help write the code, what does this repo's history prove about the checks standing between a change and the main branch?

S-3

Scoring and grades

Each dimension is a 0 to 100 answer to one concrete question, or 'could not verify' when the evidence is missing. The overall score is the weighted average of the verified dimensions, and grades band it: 90+ Elite, 75+ Strong, 60+ Developing, 40+ Early, under 40 Ad-hoc.