01 · Roasts
CI? Never Heard Of Her
116 public repos, 1046 commits this year, and not a single CI pipeline across any of the 12 analyzed repos. You clearly know how to ship — you just refuse to let machines verify it.
Paper Chaser
juzfs (GFS, 71★) and plethora (Dynamo, 80★) are both distributed systems paper implementations that popped off within days. Impressive — but at some point the world needs your *ideas*, not just Google's and Amazon's.
License? Optional, Apparently
Across 12 repos including two with 70+ stars each, licenses appear in exactly 0 of them. Congrats, your code is technically 'all rights reserved' by default. Very open source of you.
The 7-Hour Commit Sprint (relapse)
'relapse' dropped 2 commits in a 7-hour window, weighs 1865KB, has no README, no tests, no license, and no discernible purpose. Whatever relapsed, it wasn't your standards — those never showed up.
Burst Mode Activated
norway (5 days old), juzfs (6 days old), plethora (3 days old) — you build entire distributed systems faster than most people write their PRDs. Depth score says 65; timeline says 'needs therapy'.
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% weight71B
- Consistency20% weight72B
- Quality20% weight72B
- Depth15% weight70B
- Breadth10% weight72B
- Community10% weight55D
03 · Stats
365-day commit heatmap
284 active days
Language distribution
- Go47%
- Rust37%
- TypeScript12%
- Makefile1%
- C++1%
- Shell0%
- Other2%
04 · Numbers
Owned repos
non-fork
97
Commits
last 12 months
1,046
Followers
286
Joined GitHub
Jul 2023
05 · Top repos
pixperk /
juzfs
Comprehensive Rust implementation of Google File System paper with 3-component architecture, async I/O, operation logging, checkpointing, and extensive test coverage. Shipped with typed language, structured layout, and working protocols.
pixperk /
plethora
Polished Dynamo implementation in Go (80 stars, 3 days old) with complete layered architecture: vector clocks, consistent hashing, sloppy quorum, merkle tree anti-entropy, and gRPC gossip. Well-tested and typed but young.
pixperk /
chug
PostgreSQL-to-ClickHouse ETL pipeline with typed Go code, structured multi-file architecture, real-time web UI, and streaming ingestion. No tests or CI; lacks comprehensive error handling and some design documentation.
pixperk /
redis_in_rust
Full-featured async Redis clone in Rust with custom RESP parser, pub/sub, persistence, and TTL—actively developed, well-structured, but lacks tests, CI, and license.
pixperk /
norway
Early-stage reverse proxy with custom DSL, load balancing, and health checks. Clean architecture (typed Go, multi-layer compilation pipeline, radix tree routing) but minimal adoption (5 stars, 0 forks, 5 days old).
pixperk /
sptyt
Go-based Spotify-to-YouTube playlist converter with real-time WebSocket progress, multi-strategy track matching with Redis caching, OAuth token management, and analytics. Solid service architecture but thin public adoption (1 star, no external adoption signals).
pixperk /
quest
Quest is a terminal HTTP client TUI built in Go with Bubble Tea. Typed, well-documented README with structured multi-file layout (internal/ui, internal/http, internal/styles, internal/syntax), but created recently (30 days old), lacks tests/CI, no license, and minimal adoption signals.
pixperk /
jpeg-carver
Go-based JPEG carver with forensic features (SHA-256, hex dumps, truncation detection). Well-structured codebase across 5+ packages, documented README, and typed language, but no tests, CI, or license. Recent burst of work (4 commits in 4 days) suggests experimental stage.
pixperk /
cd_assgn
Complete compiler for Kira language written in Go with all 5 classic phases (lexer, parser, semantic, IR, codegen). Well-documented, typed, multi-file architecture, but very new (1 day old), no tests, and experimental assignment scope.
pixperk /
newsletter_pix
Early-stage Go newsletter service with basic subscriber management. Has README and typed language, but no tests, CI, license, or actual email sending implementation. 26 commits over ~8.5 months shows modest sustained effort on a thin, incomplete codebase.
pixperk /
pixperk
Config-only GitHub profile repo with minimal content (43 KB), no source files, sparse 2-line README. Active recent commits but no functional codebase or meaningful documentation.
pixperk /
relapse
Minimal scaffold with 1865 KB size, 2 commits in 7 hours on 2026-03-27, no README, tests, CI, docs, or license. Empty or severely underdeveloped.
06 · Timeline
- Jul 18, 2023Joined GitHub
- Feb 5, 2025Created pixperk — Config files for my GitHub profile.
- Apr 7, 2025Created redis_in_rust — a full async redis server written in rust with custom persistence, pub/sub, and key expiry
- Jun 20, 2025Created chug — high-speed ETL pipeline from PostgreSQL to ClickHouse.
- Jun 28, 2025Created quest
- Jul 13, 2025Created newsletter_pix
- Nov 4, 2025Created sptyt
- Feb 17, 2026Created plethora — implementation of dynamo storage engine in go following the original paper
- Mar 17, 2026Created juzfs — a comprehensive implementation of "The Google File System" paper in rust
- Mar 21, 2026Created norway — fast, observable reverse proxy with its own config language.
- Mar 27, 2026Created relapse
- Apr 11, 2026Created jpeg-carver
- Apr 15, 2026Created cd_assgn
- Apr 15, 2026Most recent push to jpeg-carver
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.