01 · Roasts
Test? Never Heard of Her
10 repos scored, 0 with tests. You've shipped Simon Says games, JSON parsers, AND IoT devices — and not once did you feel the urge to write a single test. That's not confidence, that's chaos.
125 Repos, 54% Abandoned
staleRepoRatio = 0.54 means over half your public repos are ghost towns. You're speedrunning the 'create repo, forget repo' pipeline. Quality > quantity, Vulcan.
0 External PRs in a Year
totalPRsYear = 0. You've been on GitHub since 2020, follow 74 people, but apparently open source is a spectator sport. Contributing upstream is how you level up.
Hardware Without a License
You're designing PCBs in KiCad, writing ESP32 firmware, publishing Fusion360 CAD files — and none of it has a license. Anyone who wants to build your screen-time device legally can't.
MAX Impact: 25/100
With 249 total stars across 125 repos, that's about 2 stars per repo on average. The portfolio exists; the audience hasn't found it yet. Maybe a README that documents the project (not just the BOM) would help.
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% weight65C
- Quality20% weight57D
- Depth15% weight58D
- Breadth10% weight72B
- Community10% weight50D
03 · Stats
365-day commit heatmap
358 active days
Language distribution
- TypeScript36%
- Python21%
- JavaScript18%
- HTML16%
- CSS9%
- EJS0%
04 · Numbers
Owned repos
non-fork
94
Commits
last 12 months
1,028
Followers
118
Joined GitHub
Aug 2020
05 · Top repos
VulcanWM /
vulcanwm
Personal portfolio site showcasing developer's 16 projects, built with Next.js + TypeScript + Tailwind. Clean component structure with animations, but README is bio-heavy without project documentation; no tests/CI. 3KB footprint, recent sustained commits through 2026.
VulcanWM /
lethe
Educational IoT device using ESP32 + IMU for screen-time reduction, with complete hardware (KiCad PCB, Fusion360 CAD) and firmware (Arduino + Python upload tool). Typed C++ with structured project layout and clear README, but unpolished, no tests/CI, and extremely nascent (16 days old).
VulcanWM /
echo
Personal hardware project: Simon Says game with RP2040 firmware, PCB/CAD design, and comprehensive documentation. Functional but early-stage indie portfolio piece with no tests/CI and unpolished codebase.
VulcanWM /
daily-dev-joke
Automated daily joke fetcher with GitHub Actions. Lightweight one-purpose tool: Node.js script pulls jokes from API daily via cron, auto-commits to README. Minimal scope, but working and deployed.
VulcanWM /
smartwatch-interface
Personal Arduino/C++ hardware project using Grove Beginner Kit. Implements smartwatch interface with password login, stopwatch, timer, clock, and sensor monitoring. ~11 hours of development with clean feature set but minimal tests, CI, or project structure.
VulcanWM /
json-parser
Educational C++ JSON parser demonstrating FSM design and stack implementation. Typed, documented, structured code with CI pipeline but no tests or license; 16 commits in 16 days.
VulcanWM /
kv-store
Simple terminal-based key-value store in C++20 with persistence via log files. Minimal scope: 3 core files (~150 LOC), no tests/CI, basic README, ~4 days old with 8 commits.
VulcanWM /
recticode-horizons-submission
Submodule scaffold for Recticode platform linking to external repos (website, CLI, API, runner, challenges). Minimal local content; 9KB size and 0 stars; functions as a pointer/aggregator rather than shipped product.
VulcanWM /
cadmus
Hardware project BOM documentation: single commit within hours of creation, 2KB repo with only README listing component sourcing for an ESP32-S3 TFT display device; minimal scope and one-shot delivery.
VulcanWM /
graph-colouring-algorithms
Minimal graph-colouring algorithm implementation (greedy & backtracking); 4 small Python files created in one burst, no README/tests/CI/license/docs, untyped code, 2KB total size.
06 · Timeline
- Aug 17, 2020Joined GitHub
- Feb 21, 2023Created vulcanwm
- Jul 1, 2023Created daily-dev-joke
- May 10, 2026Created recticode-horizons-submission
- May 15, 2026Created json-parser
- May 19, 2026Created kv-store
- Jun 21, 2026Created graph-colouring-algorithms
- Jul 15, 2026Created smartwatch-interface
- Jul 25, 2026Created echo
- Jul 29, 2026Created lethe
- Aug 16, 2026Created cadmus
- Aug 16, 2026Most recent push to cadmus
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.