01 · Roasts
Sprint King, No Follow-Through
7 of 9 repos were created and last pushed within days of each other. cost-saved-by-benford has literally 1 commit from its birthday. The GitHub heatmap looks like a heartbeat monitor for someone who naps a lot.
CI is a Myth in This Household
0 out of 9 repos have CI configured. Not one. zingPay handles Solana escrow logic and still ships with zero automated checks. 'It works on my machine' is load-bearing infrastructure here.
README: The Bare Minimum Collection
op-site's README is exactly 3 lines. cost-saved-by-benford and zingPay_demo have none at all. You're building a Solana payment protocol and a cryptography library with the documentation ambition of a sticky note.
Crypto Library, No Tests, No Audit, No Problem
shamirsecret's own README says it's 'not audited for production use' and lists 'Test cases' under 'Somethings to cover.' Aspirational TODO-driven security engineering.
4-Month Veteran, 39 Repos
Joined GitHub in January 2025 and already has 39 public repos — that's roughly 2 repos per week. Most are single-burst sprints. Quantity is clearly not the bottleneck here.
Built using
Zoral
Shadows one worker for a week, then takes over their job with zero extra setup. Behaves exactly like the original.
zoral.ai
02 · Category breakdown
- Impact25% weight56D
- Consistency20% weight55D
- Quality20% weight57D
- Depth15% weight45D
- Breadth10% weight65C
- Community10% weight50D
03 · Stats
365-day commit heatmap
78 active days
Language distribution
- TypeScript60%
- Rust15%
- JavaScript10%
- Jupyter Notebook8%
- CSS3%
- HTML2%
- Other2%
04 · Numbers
Owned repos
non-fork
25
Commits
last 12 months
101
Followers
15
Joined GitHub
Jan 2025
05 · Top repos
owlpharoah /
zingPay
Early-stage Solana payment protocol using phone numbers as wallet IDs. Typed, documented full-stack prototype (Rust Anchor, Node.js, Next.js) with core escrow + direct transfer logic, but under 2 weeks old with minimal real-world validation.
owlpharoah /
mb_gql_server
A GraphQL API wrapper for MusicBrainz built in Rust with Redis caching and DataLoader batching. Small, early-stage project (33 KB, ~1 month old, 4 commits) with solid core concepts but no tests, CI, or license.
owlpharoah /
op-site
Personal website project in HTML with minimal documentation. 6.6 MB codebase showing ~14 months of development (16 commits in last 30), but lacks tests, CI, license, structured documentation, and type safety. Clear personal project with modest scope.
owlpharoah /
shamirsecret
Educational Shamir's Secret Sharing implementation in Rust with AES-GCM file encryption. Unaudited demo code with hardcoded parameters, no tests/CI, and limited real-world adoption (3 stars).
owlpharoah /
portal
Early-stage monorepo alumni directory with Next.js frontend and Express backend. Functional API with basic validation, but frontend is unimplemented boilerplate; no tests, no CI/CD, no license.
owlpharoah /
lobstorrent
Fresh Rust TUI tool for torrent search using ratatui + tokio, with README but minimal commit history (3 of 30). Typed, no tests/CI. Created Feb 27, 2026; less than 1 day old with thin execution depth.
owlpharoah /
math
Educational math library implementing finite fields and elliptic curves in Rust. Typed language with structured multi-module layout (fields_and_curves/, number_theory/) but lacks documentation, tests, CI, license, and has minimal recent activity (3 of last 30 commits).
owlpharoah /
cost-saved-by-benford
Minimal educational Rust code exploring information theory and Benford's Law with a single main.rs file, no README, tests, CI, or documentation. Single commit on creation day.
owlpharoah /
zingPay_demo
Minimal demo repo created today with 7 commits, no README, no documentation, no CI, and no license. TypeScript + tests present but insufficient to establish a working project without context.
06 · Timeline
- Jan 13, 2025Joined GitHub
- Feb 22, 2025Created op-site — Personal Website
- Feb 7, 2026Created mb_gql_server — graphql server for musicbrainz api
- Feb 27, 2026Created lobstorrent — A cli tool to find blazing fast torrents
- Mar 11, 2026Created math
- Apr 3, 2026Created zingPay — powered by paYlaB
- Apr 5, 2026Created zingPay_demo
- May 9, 2026Created cost-saved-by-benford — How much did Benford's Law actually save us? All calculated in code.
- May 10, 2026Created shamirsecret — Shamir's Secret Sharing Algorithm implemented in rust
- May 18, 2026Created portal
- May 24, 2026Most recent push to portal
07 · Compare
08 · Rubric
How this score was produced
Overall = Σ (category × weight) + gentle top-end curve
Tier thresholds
▸ How the pipeline works
- 01Scrape.Pull every non-fork repo pushed in the last 90 days, plus your contribution calendar, followers, and language byte counts — straight from GitHub's REST & GraphQL APIs.
- 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
- 03Grade each repo. All repos run in parallel through a fast scoring model that reads the picked files and rates each one independently on Impact, Quality, and Depth — with evidence citations.
- 04Aggregate. A larger reasoning model combines the per-repo scores with server-computed stats (heatmap, commit cadence, language entropy, follower count) to produce the 6-dimension profile score + roasts.
- 05Correct.Deterministic server-side checks enforce anchor-scale floors (e.g. a profile with 2,000+ public commits can't score 30 Consistency) and recompute the final verdict.
~90 seconds per profile, ~$0.25 in compute. Total of ~240 files read across your top-12 repos. One rating per GitHub account per day.
▸ Data sources & caveats
- Heatmap & commit totals: GitHub GraphQL
contributionsCollection— covers the last 365 days, includes private repos when the user has opted in (default). - Language %: byte totals across the top 30 owned non-fork repos.
- Curve: a small upward nudge centered on raw score ≈ 70, capping at 100. Prevents specialists from being unfairly penalised for narrow breadth.
- Anchor corrections: when server-measured signals (e.g. privateWorkLikely, multiRepoVolume, follower count) mandate a minimum category score, the aggregation step enforces it. These are signal-conditional, not identity-based floors.