01 · Roasts
Graveyard of Good Intentions
emailpersonalizer, gitscorer, and 3jsclouds collectively have 5 commits, 0 KB of actual code, and lifespans measured in seconds-to-hours. They exist purely to haunt your repo list.
TypeScript Monoculture
95% TypeScript. The 2% Java is literally one school assignment. Your language diversity is essentially: TypeScript, TypeScript, and Academic Java.
Portfolio × 2 (Neither Finished)
You have repos named 'portfolio' AND 'portfolio2' — the original committed for 3 weeks before being abandoned, and the sequel was birthed and buried in 3 minutes. Third time's the charm?
3 Followers, 1356 Commits
You shipped 1,356 commits this year across a monorepo, a formal-verification library, and a JavaFX app — and somehow only 3 people noticed. The commits are real; the audience is imaginary.
Scaffold Collector
4 of your 10 repos are pure initialization scaffolds (gitscorer, emailpersonalizer, 3jsclouds, jverene). That's a 40% graveyard rate for someone who's been on GitHub less than 8 months.
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% weight58D
- Consistency20% weight65C
- Quality20% weight72B
- Depth15% weight65C
- Breadth10% weight55D
- Community10% weight25F
03 · Stats
365-day commit heatmap
93 active days
Language distribution
- TypeScript95%
- JavaScript2%
- Java2%
- Lean0%
- Svelte0%
- Shell0%
- Other1%
04 · Numbers
Owned repos
non-fork
10
Commits
last 12 months
1,356
Followers
3
Joined GitHub
Sep 2025
05 · Top repos
jverene /
cracked-coder
Fully-featured TypeScript orchestration CLI backed by Gemini, with comprehensive testing, CI/CD, docs, and Apache 2.0 license. Ships as @google/cracked-coder npm package with weekly stable releases and free tier access.
jverene /
adaptive-bitmask
Specialized TypeScript library for multi-agent bitmask-based coordination with sub-10ms latency claims, comprehensive docs, tests, CI/CD, and formal Lean verification of core protocol properties.
jverene /
kuda-focus-apcs
APCS student project: functional JavaFX focus timer with process monitoring, streak tracking, and OOP demonstrations. Typed Java, documented, structured architecture, tested. Active portfolio work showing multi-component integration.
jverene /
portfolio2
Personal portfolio site with React, Three.js 3D rendering, and GSAP animations. Minimal commit history (5/30), incomplete product (placeholder content, commented routes), but typed language and structured multi-file layout with meaningful visuals.
jverene /
webreader
Early-stage Svelte-based ebook reader app that syncs chapters from Google Drive folders into a Supabase backend with customizable reading UI. Typed, structured, and documented in PRD.md, but pre-release with 0 stars and minimal git history (1 of last 30 commits sampled).
jverene /
portfolio
Personal portfolio website with minimal documentation (README is one line), JavaScript, tests present but no CI/license/gitignore. 17.8MB codebase with 3 commits in last 30 days suggests early-stage personal project.
jverene /
jverene
Profile repo with ASCII art and GitHub stat badges; 0 stars, 18 KB, 6 commits in 2 days. No source code, no tests, no CI, no license, no meaningful documentation beyond aesthetic display.
jverene /
3jsclouds
Minimal CodeSandbox experiment with no stars, 0 commits after creation, empty README, no tests/CI/license, and no source files fetched. Scaffold-stage project.
jverene /
emailpersonalizer
Empty scaffold project: 0 KB size, single commit, minimal README (11 words), no source files, no tests/CI/license. Appears to be initial repo setup only.
jverene /
gitscorer
Empty scaffold repo created 2026-04-06 with only a bare README title, no implementation, tests, CI, license, or meaningful documentation. One commit in 35 seconds suggests a placeholder-only initialization.
06 · Timeline
- Sep 18, 2025Joined GitHub
- Jan 28, 2026Created kuda-focus-apcs — apcs app
- Feb 18, 2026Created adaptive-bitmask — Library allowing efficient multi-agent coordination and shared cognition. Built on Adaptive Bitmask Protocols
- Feb 26, 2026Created portfolio — personal website
- Mar 14, 2026Created cracked-coder — perfect, legal, free tier orchestration cli
- Apr 6, 2026Created gitscorer
- Apr 7, 2026Created emailpersonalizer — personalize email scripts for the sports bridge outreach
- Apr 15, 2026Created portfolio2
- Apr 15, 2026Created webreader
- Apr 24, 2026Created 3jsclouds — Created with CodeSandbox
- Apr 25, 2026Created jverene
- Apr 27, 2026Most recent push to cracked-coder
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.