01 · Roasts
The Test Desert
117 repos, 117 repos scored, ZERO have HAS_TESTS=yes. Not one. You've got CI pipelines running... nothing. It's like installing a smoke detector with no battery.
Placeholder Pusher
queue-simulator and key-value-store were created AND pushed within seconds — one contains `print('queue simulator')`, the other has 'Hello, world!'. GitHub commits aren't the same as writing code, chief.
Stars in the Wrong Galaxy
258 total stars across 117 repos averages 2.2 stars each. Your portfolio site has 6 stars. Your daily joke bot has 5. The math is doing math.
CI Without a Safety Net
You wired up GitHub Actions in 5 repos — daily-dev-joke, blackjack, memoryexplorer, specscraper, stem-sims — but none of them run tests because there are no tests to run. That's a CI pipeline with zero CI.
60% Abandoned
staleRepoRatio=0.60 — more than half your repos haven't been touched in 2+ years. You're not a developer with 117 projects, you're a developer with ~47 projects and a graveyard.
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% weight52D
- Depth15% weight58D
- Breadth10% weight75B
- Community10% weight55D
03 · Stats
365-day commit heatmap
363 active days
Language distribution
- TypeScript36%
- Python21%
- JavaScript18%
- HTML16%
- CSS9%
- EJS0%
04 · Numbers
Owned repos
non-fork
93
Commits
last 12 months
893
Followers
117
Joined GitHub
Aug 2020
05 · Top repos
VulcanWM /
vulcanwm
Personal portfolio site built with Next.js, TypeScript, and Tailwind CSS featuring animated hero sections and project showcase. Well-typed and structured but lacks tests, CI, and deployment automation. README is personal bio rather than project documentation.
VulcanWM /
stem-sims
Early-stage collaborative math simulation library with 5 Python implementations (page_rank, coin_toss, random_walk, text_prediction, card_shuffling), CI/CD pipeline, but no tests, no license, untyped Python, and minimal external polish.
VulcanWM /
daily-dev-joke
Lightweight automation project that fetches jokes via API and auto-updates README daily. Untyped JavaScript with CI workflow but no tests or license. Simple, functional implementation with persistent commits over 2+ years.
VulcanWM /
Platform
Minimal iOS breathing app for train journeys, built in SwiftUI with light/dark mode support. Clean single-purpose design with onboarding flow, but early-stage—zero stars, no tests/CI, modest codebase (~55KB).
VulcanWM /
memoryexplorer
Experimental C benchmark comparing three data structures (dynamic array, linked list, hash table) for leaderboard operations. Minimal scope, no license, no tests, but working CI builds and basic documentation.
VulcanWM /
blackjack
Learning-focused C++ OOP Blackjack game with CI/CD pipeline and personality typing feature. Well-structured classes, strict compilation flags, and CMake build system, but young (10 days), no tests, no license, and minimal documentation beyond README.
VulcanWM /
blackjack-gamejam
Blackjack game built with React, TypeScript, and Vite for a game jam. Single-file implementation with game logic, no tests or CI. Untouched boilerplate README and basic structure.
VulcanWM /
specscraper
Early-stage educational web scraper for AQA Physics specs (21 KB, 20 of 30 recent commits). Single-file tool with CI but no tests, untyped Python, and known parsing limitations acknowledged by author.
VulcanWM /
specmap
Brand-new Next.js learning tool for AQA A-Level Physics with RAG status tracking. TypeScript typed but lacks documentation, tests, CI, and license. 5 commits in ~2 days; minimal GitHub visibility (0 stars).
VulcanWM /
key-value-store
Empty Rust scaffold with only "Hello, world!" boilerplate. No README, tests, CI, docs, license, or gitignore. Created and pushed same day with minimal commit activity.
VulcanWM /
queue-simulator
Empty scaffold with single print statement, no documentation, tests, CI, or meaningful code. Created and pushed same day with 1 commit across 15 seconds.
06 · Timeline
- Aug 17, 2020Joined GitHub
- Feb 21, 2023Created vulcanwm
- Jul 1, 2023Created daily-dev-joke
- Jan 10, 2026Created stem-sims — a collaborative, open source collection of mathematical simulations implemented in multiple programming languages.
- Jan 21, 2026Created memoryexplorer
- Jan 22, 2026Created Platform
- Feb 19, 2026Created specscraper
- Feb 21, 2026Created specmap
- Feb 23, 2026Created blackjack
- Feb 28, 2026Created blackjack-gamejam
- May 1, 2026Created key-value-store
- May 1, 2026Created queue-simulator
- May 8, 2026Most recent push to daily-dev-joke
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.