01 · Roasts
Distributed systems, distributed safeguards
DukeDB runs five-node integration tests, but several neighboring projects still ship with the tests/CI/license trifecta set to absent.
The C server brought receipts
HTTP_in_C claims 21,432.46 requests/sec in ApacheBench, then leaves a noted free_request segfault in the codebase.
Portfolio has portfolio
baltej.me is 69,519 KB with a 30/30 recent-commit sample; the portfolio is getting more exercise than its test suite.
Builder throughput is real
595 yearly commits and 162 multi-repo-volume say you ship constantly; 71 total stars say the audience is still loading.
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% weight69C
- Depth15% weight58D
- Breadth10% weight65C
- Community10% weight55D
03 · Stats
365-day commit heatmap
197 active days
Language distribution
- Python82%
- JavaScript7%
- Makefile3%
- TypeScript2%
- CSS2%
- C++1%
- Other3%
04 · Numbers
Owned repos
non-fork
81
Commits
last 12 months
595
Followers
93
Joined GitHub
Oct 2020
05 · Top repos
baltej223 /
dukedb
DukeDB is a substantial Go distributed key-value database with gossip membership, routing, replication, TCP messaging, HTTP APIs, SDK-driven integration tests, and CI, but adoption remains limited at 11 stars.
baltej223 /
duke-orchestrator
A documented Go orchestrator that reconciles local DukeDB nodes, supports native and Docker execution plus multiplexed or isolated logging, with GitHub Actions builds but no test files or license.
baltej223 /
baltej.me
A substantial Next.js portfolio with multiple pages, reusable UI components, animations, a blog, and a Spotify API route, but no tests, CI, license, or typed code and limited evidence of adoption.
baltej223 /
duke-client
Small JavaScript SDK with documented DukeDB connectivity, health checks, failover, GET/PUT, and batching, but limited validation through tests or automation.
baltej223 /
opencl-rs
Small OpenCL GPU experiment with Rust FFI, C runtime, Docker GPU setup, and GitHub Actions, but limited adoption and several correctness and robustness gaps.
baltej223 /
java_academic
A small Java coursework repository containing five assignment areas, including console exercises, food-order polymorphism, library resources, and exception-handling demos; it is structured across packages but lacks documentation, tests, CI, and licensing.
baltej223 /
HTTP_in_C
A documented, multi-file C HTTP/1.1 learning server with benchmarked throughput, but adoption is minimal and the implementation lacks tests, CI, licensing, and robust error/memory handling.
baltej223 /
baltej223
A maintained GitHub profile-configuration repository with a README, two scheduled automation workflows, and linked personal publishing sites, but no tests, license, or substantive application code.
baltej223 /
software_engineering_project
Atlas is a documented early-stage personalization-engineering project with substantial architecture and workflow diagrams, but no implemented typed code, tests, CI, license, or evidence of adoption.
baltej223 /
dev_vim
A tiny, documented Rust CLI scaffold for checking local devcontainer files, with basic clap argument parsing but minimal functionality and no validation or adoption evidence.
baltej223 /
nodemon_for_C
A small documented Linux C watcher that recompiles and runs a source file via inotify, fork, and gcc, but has no tests, CI, license, or demonstrated adoption.
baltej223 /
cloud_computing_test_repo
A temporary cloud-computing lab repository containing only a minimal README and an empty C main function, with no tests, CI, license, or evident adoption.
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
- Mar 24, 2026Created HTTP_in_C — HTTP/1.1 server from scratch in C: 21K req/s, sub-5ms latency, no libraries
- 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 22, 2026Created opencl-rs — Rust FFI bindings to OpenCL, and dev container setup for openCL + Intel GPUs
- Jul 31, 2026Created java_academic — Course Material of UCS553P ( Enterprise Web applications)
- Aug 13, 2026Created nodemon_for_C — Watch mode and auto compile on changes, for C!
- Aug 24, 2026Created cloud_computing_test_repo — Just a temp repo created during cloud comuting lab
- Sep 2, 2026Created software_engineering_project — Software engineering project: Altas personalisation engine!
- Sep 13, 2026Created dev_vim — Run devcontainer in your neovim.
- Sep 15, 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.