01 · Roasts
CI/CD? Never Heard Of Her
Zero out of 7 repos have CI enabled. You're shipping a SaaS with PayPal integration and a full game engine, but a green checkmark remains a mythical creature in your GitHub account.
The 1-Day SaaS Sprint
subscription-managemnet (yes, with the typo) has 15 PostgreSQL tables, multi-currency invoicing, and a subscription lifecycle manager — built in a single day. The ambition is genuinely impressive. The 0 stars suggest you forgot to tell anyone it exists.
Test Coverage: Vibes Only
Across all 7 repos, HAS_TESTS=no every single time. packet-drift has 12 hand-written test cases in a README doc, which is adorable but not a test suite. Your bugs are living their best life undetected.
Heatmap Hibernation Mode
The first 30 weeks of your heatmap look like a flatline EKG with occasional spasms. Only in the last ~15 weeks did you remember GitHub exists. Better late than never, but your commit history reads like a semester syllabus.
Stars: Collecting Dust
9 total stars across 22 repos, with os-algorithms carrying 3 of them. You're building voice AI for farmers, full-stack SaaS, and game engines with DP algorithms — and the community response has been a collective shrug. Ship louder.
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% weight80A
- Community10% weight50D
03 · Stats
365-day commit heatmap
177 active days
Language distribution
- TypeScript47%
- Python21%
- JavaScript13%
- CSS7%
- Java4%
- C++4%
- Other4%
04 · Numbers
Owned repos
non-fork
20
Commits
last 12 months
323
Followers
40
Joined GitHub
Jul 2024
05 · Top repos
Nithin0306 /
packet-drift
A course project for Design & Analysis of Algorithms (DAA) implementing a 2-player inertia-based game with AI using Greedy, Divide & Conquer, and Dynamic Programming techniques. Typed Java with clear structure, documentation, and algorithmic focus, but limited to academic scope without external adoption.
Nithin0306 /
subscription-managemnet
Early-stage subscription management SaaS with full-stack TypeScript architecture, PostgreSQL schema with 15+ tables, auth/payment integrations, but newly created (1 day old), no tests/CI, lacks README. Structured for production but unproven adoption.
Nithin0306 /
KisanMitra
Voice-first agricultural assistant for Indian farmers with Gemini LLM, deterministic rule engines, and React Native Expo frontend. Recent hackathon prototype with 0 stars, minimal public visibility, but solid typed TypeScript/Python architecture.
Nithin0306 /
portfolio-website
Personal portfolio website in TypeScript/Next.js with terminal widget, project showcase, and RAG/AI project examples. Typed, documented, and structured but no tests/CI and minimal adoption (0 stars).
Nithin0306 /
codeforces
Personal collection of Codeforces competitive programming solutions in C++. No documentation, tests, or CI. ~30 commits over 6 months with basic algorithmic problems. Minimal project structure; lacks README and any supporting documentation beyond code.
Nithin0306 /
os-algorithms
Early-stage educational OS algorithms repository in C (40KB, 3 stars). Has README and GPL-3.0 license, but no tests, CI, or source file samples. Only 11 days old with 24/30 recent commits; lacks implemented depth.
Nithin0306 /
Nithin0306
GitHub profile configuration repo with only a README containing personal branding and skill badges. No functional code, tests, CI, or meaningful project substance. Pure profile documentation.
06 · Timeline
- Jul 23, 2024Joined GitHub
- Oct 15, 2024Created Nithin0306 — Config files for my GitHub profile.
- Sep 14, 2025Created codeforces — A collection of my solutions to Codeforces problems.
- Dec 15, 2025Created packet-drift — Packet Drift — A 2-player inertia-based game built for the DAA (23CSE211) course, designed to explore multiple algorithmic strategies.
- Feb 7, 2026Created subscription-managemnet — A subscription management platform to handle products, subscriptions, invoices, and payments with proper business logic.
- Feb 23, 2026Created os-algorithms — Practical implementations of core Operating System concepts in C, focused on processes, concurrency, and synchronization.
- Mar 21, 2026Created portfolio-website
- Apr 13, 2026Created KisanMitra — Hackathon prototype for smart farming and farmer support
- Apr 16, 2026Most recent push to KisanMitra
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.