01 · Roasts
Test Coverage: Statistically Zero
Out of 12 analyzed repos, exactly ONE has tests — a fork of github-readme-stats where you didn't write them. Meanwhile duke-client ships with a bug that crashes batch operations (undefined 'db' on lines 94 and 113). Ship fast, break things, fix never.
The One-Day Repo Factory
opencl-rs: 1 day. duke-orchestrator: 1 day. openCL_devcontainer: 4 hours. You've turned 'git init' into a hobby — 80 public repos but staleRepoRatio is only 0.07, meaning you're somehow actively abandoning them at speed.
Cargo.toml Edition 2024 Doesn't Exist
opencl-rs has `edition = '2024'` in Cargo.toml, which is not a valid Rust edition. You also used unwrap() on CString::new() in what is literally a 4KB repo. The bugs-per-kilobyte ratio is impressive.
81% Python, 0% Python Tests
Python is 81% of your language footprint but zero Python repos in the sample have test coverage. You've written gradient descent code with commented-out sections and PascalCase method names in Rust. The algorithm is correct; the code review is not.
91 Followers, 3 PRs to Show for It
You've accumulated 91 followers somehow, but contributed 3 external PRs all year. That's a follower-to-PR ratio of 30:1. Your audience is more productive than you are at contributing back.
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% weight57D
- Depth15% weight58D
- Breadth10% weight65C
- Community10% weight55D
03 · Stats
365-day commit heatmap
195 active days
Language distribution
- Python81%
- JavaScript8%
- Makefile3%
- TypeScript2%
- CSS2%
- C++1%
- Other3%
04 · Numbers
Owned repos
non-fork
75
Commits
last 12 months
616
Followers
91
Joined GitHub
Oct 2020
05 · Top repos
baltej223 /
Mirage
AR treasure hunt game with typed React+Express stack deployed at Thapar college event. Functional full-stack project with geolocation gameplay, structured frontend/backend, and documentation; lacks automated tests and CI infrastructure.
baltej223 /
dukedb
Distributed key-value database learning project with typed Go, structured multi-file layout, gossip-based clustering, and HTTP API; lacks tests/CI and maintains minimal adoption (3 stars), but demonstrates architectural scope and intentional design.
baltej223 /
baltej.me
Personal Next.js portfolio site (68MB) with 30 recent commits and alternate documentation (ARCHITECTURE.md, STATUS.md), but no tests, CI, or actual portfolio content visible. Untyped JavaScript with create-next-app boilerplate README.
baltej223 /
HTTP_in_C
Personal HTTP/1.1 server written in C from scratch; untyped language with README and structured codebase, but no tests, CI, or license. ~2-month burst of 18 recent commits building a functional networking project, but minimal external adoption.
baltej223 /
duke-orchestrator
Go orchestrator for multi-node local deployment; typed, structured, minimal docs. Fresh project (1 day old) with basic orchestration logic and YAML config support, but no tests, CI, or established audience.
baltej223 /
posts.baltej.me
Personal blog/posts site built with Next.js + MDX. Single star, minimal documentation in README with TODOs listed, no tests/CI. Typed infrastructure with Express backend and file management scripts, but thin public output and no license.
baltej223 /
github-readme-stats
Fork of popular github-readme-stats with minimal original work; 1 star, 3 commits in ~6 weeks, MIT licensed with docs but no source files available for inspection.
baltej223 /
duke-client
Lightweight Duke DB JavaScript SDK with core GET/PUT operations and health checking. Untyped, no tests/CI, minimal implementation (7 KB, ~150 LOC). Shows functional API design but lacks robustness for production use.
baltej223 /
algoss
Personal educational repo implementing gradient descent (Rust), bisection, and binary search trees (C) with minimal documentation, no tests or CI, and unpolished code structure.
baltej223 /
opencl-rs
Minimal Rust FFI wrapper around OpenCL C implementation. ~4KB repo with ~2 recent commits; basic working library but no tests, CI, license, or error handling. One-week sprint quality.
baltej223 /
openCL_devcontainer
Minimal devcontainer scaffold for OpenCL development; 513 KB codebase with 2 commits in 4 hours, no tests, no CI, and 2-line README providing only usage instructions without project context.
baltej223 /
baltej223
GitHub profile configuration repo with README showcasing skills and social links; minimal code content, experimental one-off commit history pattern.
06 · Timeline
- Oct 21, 2020Joined GitHub
- Apr 6, 2022Created baltej223 — Config files for my GitHub profile.
- Dec 8, 2024Created baltej.me — Baltej Singh's Portfolio
- May 27, 2025Created posts.baltej.me — A place where I post my "posts" on posts.baltej.me
- Nov 4, 2025Created Mirage — AR treasure hunt game deployed at a live college event: players navigate physically using phone camera to find hidden chests and score points
- Dec 14, 2025Created algoss — Implementation of some intrusting algos
- Mar 24, 2026Created HTTP_in_C — HTTP/1.1 server from scratch in C: 21K req/s, sub-5ms latency, no libraries
- May 9, 2026Created github-readme-stats
- May 18, 2026Created dukedb — DukeDB is a distributed lightweight key-value database with, decentralized node communication, gossip-based cluster coordination, replication
- Jun 10, 2026Created duke-client — JS client (sdk) for Duke distributed db.
- Jun 19, 2026Created duke-orchestrator — A single orchestrator for multiple duke nodes, running on the single local machine.
- Jun 20, 2026Created openCL_devcontainer — OpenCL devcontainer config for Intel IrisX.
- Jun 22, 2026Created opencl-rs — Rust FFI bindings to OpenCL, and dev container setup for openCL + Intel GPUs
- Jun 25, 2026Most recent push to baltej223
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.