01 · Roasts
226 Repos, Zero Licenses
You have 226 public repos and apparently zero interest in licensing any of them. Legal void enthusiast. Someone could steal your entire payment systems portfolio and you'd have no recourse — though with 0 stars each, they probably won't bother.
Sprint Dev Syndrome
stock_ecomm: 13 minutes. upi-apps: 31 minutes. vpn-cf-workers: 2 minutes. Your repos have better commit timestamps than a parking meter. The architecture is genuinely impressive; it's the 'done in one sitting and never touched again' part that's the problem.
CI? Never Heard of Her
Zero repos out of 12 analyzed have CI enabled. You built a fraud detection engine, a BNPL scoring system, and a UPI saga executor — but not a single GitHub Actions workflow. The tests exist; they just run on vibes.
binary-market-stream
Created 2026-04-02 at 21:16:16Z. Last commit: 21:16:17Z. One second of effort. The repo name is ambitious; the contents are a README title and a dream. This is the platonic ideal of the placeholder commit.
waht-i-am-learning
29 commits over 5 months to a bookmark file — and you still can't spell 'what'. You've committed more to your reading list than to any actual project. Dedication is its own form of irony.
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% weight48D
- Consistency20% weight65C
- Quality20% weight57D
- Depth15% weight50D
- Breadth10% weight65C
- Community10% weight50D
03 · Stats
365-day commit heatmap
304 active days
Language distribution
- Rust38%
- Go37%
- TypeScript16%
- C3%
- CSS2%
- JavaScript1%
- Other3%
04 · Numbers
Owned repos
non-fork
59
Commits
last 12 months
752
Followers
123
Joined GitHub
Sep 2023
05 · Top repos
Bhup-GitHUB /
Fraud-payments
Go-based fraud detection microservices prototype with payment authorization flow, risk scoring engine, and Kafka streaming. Typed, documented, modular architecture with tests but experimental—repo created 20 hours ago, 4 commits, no license or CI.
Bhup-GitHUB /
stock_ecomm
Rust e-commerce stock management service built with Axum and Tokio. Demonstrates solid architectural patterns with typed models, async concurrency primitives, and event streaming—but lacks documentation, tests integration, and external adoption signals.
Bhup-GitHUB /
decomposed-eng
Go prototype ETA engine for food delivery with HTTP API, decomposed calculation modules, and test coverage. Created/updated same day (6 KB). A small working typed project with clear structure and tests, but no sustained development signal.
Bhup-GitHUB /
upi-apps
Go-based UPI payment system prototype demonstrating saga pattern, idempotency, and distributed transaction logic across modular packages; minimal adoption, created and last pushed same day.
Bhup-GitHUB /
BNPL
Fresh BNPL instant approval backend prototype built in Go with gRPC, Postgres, concurrent provider orchestration, scoring/rules engines. Newly created (34KB, 3 commits in <1 hour), no tests ran yet, minimal real-world adoption.
Bhup-GitHUB /
paytm-balance
Minimal money transfer API in Go with basic endpoints for transfers and balance queries. Single-day creation with 4 commits, no tests, no CI, no license. Demonstrates idempotency and arbitrary-precision arithmetic but lacks documentation depth.
Bhup-GitHUB /
cricket-streaming
Prototype Go streaming API with clean architecture (chi, postgres, redis) but ultra-early stage: 1 star, no README, no tests/CI, created 2 hours ago with single commit. Typed and structured but unproven.
Bhup-GitHUB /
reconciliation-phonpe
Zero-star prototype payment reconciliation API built in Go. Has basic typed code structure, REST endpoints, and PostgreSQL schema, but minimal commits (1 of last 30), no tests, no CI, and no license—traits of a one-off technical scaffold.
Bhup-GitHUB /
waht-i-am-learning
A personal learning notes repository containing only a README with curated links to videos, articles, and external resources—no substantive code, no structure, minimal intrinsic value beyond bookmark collection.
Bhup-GitHUB /
Operating-System-Lab
Empty scaffold with 4 commits over 14 days, no README, tests, CI, or documentation. 33 KB JavaScript project with no meaningful output or adoption signals.
Bhup-GitHUB /
vpn-cf-workers
Minimal scaffold repo created 2026-04-05, 2 commits in 2 minutes, 108 KB total. README title only, no code files sampled, no tests/CI/license. Appears to be an empty project initialization.
Bhup-GitHUB /
binary-market-stream
Empty scaffold repo with minimal README, zero commits after creation, no source files, tests, CI, or license. Meets empty-repo anchor criteria.
06 · Timeline
- Sep 21, 2023Joined GitHub
- Oct 7, 2025Created waht-i-am-learning — plans for next 2 mnths
- Mar 23, 2026Created decomposed-eng
- Mar 28, 2026Created BNPL
- Apr 1, 2026Created Operating-System-Lab
- Apr 2, 2026Created binary-market-stream
- Apr 2, 2026Created Fraud-payments
- Apr 2, 2026Created paytm-balance
- Apr 5, 2026Created vpn-cf-workers
- Apr 5, 2026Created upi-apps
- Apr 7, 2026Created reconciliation-phonpe
- Apr 17, 2026Created cricket-streaming
- Apr 20, 2026Created stock_ecomm
- Apr 20, 2026Most recent push to stock_ecomm
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.