01 · Roasts
One-Week Wonder Factory
SnapNStore, MiniDB, MiniEditor, MiniContainer, MiniGit, MiniSniffer — all built in under a week each. Incredible velocity, zero stars. You're shipping to a stadium with no audience.
CI Allergic
Out of 9 scored repos, exactly ONE has CI. SnapNStore has it and it's genuinely impressive. The other eight are running on vibes and -Werror. That's not a pipeline, that's optimism.
C Monoculture
80% of your codebase is C. You've built a database, a container runtime, a VCS, a packet sniffer, and a text editor — all in C. Respect. Also: have you considered touching grass in another language?
Account Is 11 Months Old and Already Exhausting
Joined July 2025, 289 commits, 9+ projects. You've built more infrastructure in less than a year than most engineers touch in five. Unfortunately GitHub still shows 4 followers and 0 stars.
31 PRs, 0 Issues
You opened 31 pull requests this year and zero issues. Either every repo you contribute to has perfect code, or you're just merging your own branches and calling them PRs. The heatmap suggests the latter.
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% weight62C
- Consistency20% weight65C
- Quality20% weight72B
- Depth15% weight65C
- Breadth10% weight55D
- Community10% weight25F
03 · Stats
365-day commit heatmap
45 active days
Language distribution
- C80%
- Java12%
- JavaScript6%
- CSS1%
- Makefile1%
- Shell0%
04 · Numbers
Owned repos
non-fork
13
Commits
last 12 months
289
Followers
4
Joined GitHub
Jul 2025
05 · Top repos
finn-abel /
SnapNStore
SnapNStore: a well-architected, feature-complete local snapshot backup tool in C with comprehensive documentation, full test suite, and robust encryption/compression pipeline. Personal project with no external adoption yet.
finn-abel /
MiniDB
Self-contained relational database in C with full SQL pipeline (lexer→parser→binder→planner→executor), B+ tree indexes, WAL recovery, and comprehensive test suite covering storage, execution, transactions, and recovery.
finn-abel /
MiniGit
Educational C11 VCS implementation with core Git features (commits, branches, merges, diffs). Typed, well-tested, documented. Very recent creation (June 2026) with solid architecture but no real-world adoption.
finn-abel /
MiniContainer
Educational Linux container runtime in C with CLI, namespaces, cgroups, networking, and port publishing. Minimal adoption but well-architected for learning.
finn-abel /
MiniEditor
Terminal text editor in C11 with clean architecture, undo/redo, syntax highlighting, and structured tests. Early-stage personal project with no external adoption yet.
finn-abel /
MiniSniffer
Well-crafted C packet sniffer with libpcap integration, comprehensive filtering, TCP reassembly, and application-layer decoding (HTTP/DNS/TLS). Clean architecture with 20+ test files but limited adoption (0 stars, <6 days old).
finn-abel /
bot-trap-server
Specialized passive bot-observation backend with dual Cloudflare Workers + Node.js architecture, SQLite + D1 storage, IP enrichment, and authenticated dashboard API. Early-stage project (5 days old, 6 commits) addressing niche security use case with clean structure and tests.
finn-abel /
timekeeper
Internal timekeeping tool built with React, Express, PostgreSQL. Functional full-stack project with proper structure, but unpolished production readiness. No tests, CI, or security hardening. 0 stars; created 3 days ago.
finn-abel /
bot-trap-dashboard
Fresh (4-day-old) local-only dashboard for bot-trap-server. React+Vite with Tailwind, TanStack Query/Table. Has tests and structured layout; no CI, untyped JS, minimal public adoption (0 stars). Well-intentioned but too new and purpose-scoped to demonstrate sustained shipping.
06 · Timeline
- Jul 2, 2025Joined GitHub
- May 16, 2026Created MiniDB — MiniDB: Self-contained relational database built in C
- Jun 1, 2026Created timekeeper
- Jun 8, 2026Created MiniSniffer — MiniSniffer: Packet sniffer and network analyzer built in C
- Jun 11, 2026Created MiniGit — MiniGit: A simple version control system built in C
- Jun 13, 2026Created bot-trap-server — Hands out bait URLs you hide in GitHub repos and logs what bots reveal when they fetch them.
- Jun 13, 2026Created bot-trap-dashboard — Dashboard for exploring the bots caught by bot-trap-server.
- Jun 17, 2026Created MiniContainer — MiniContainer: Simple linux container runtime
- Jun 22, 2026Created MiniEditor — MiniEditor: Terminal based text editor for C files
- Jun 23, 2026Created SnapNStore — SnapNStore: A lightweight C project for capturing, organizing, and storing snapshots with a focus on simplicity, speed, and local-first control.
- Jun 28, 2026Most recent push to SnapNStore
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.