01 · Roasts
CI? Never heard of her.
Zero CI pipelines across all 7 scored repos. You have tests in GO-DFS and charya, but they run exclusively on your laptop. GitHub Actions costs $0 and takes 10 minutes — you're not too busy, you're too comfortable.
63% Jupyter Notebook
Your language breakdown is two-thirds .ipynb files, yet your domain is listed as 'systems.' You're building distributed file systems in Go while your byte count is screaming 'data science homework.' The notebooks are the real you.
The 48-Hour Sprint Factory
csl: created and last-pushed on the same day. charya: 3 commits in 2 days. You have a pattern of shipping elaborate READMEs into brand-new repos and then moving on. A repo isn't a portfolio piece until it has a second week.
5 Stars, 0 Licenses
GO-DFS has 5 stars — your most-loved project — and no license. Legally, nobody can use it, fork it, or contribute to it. Those 5 stargazers are admiring a project they're not allowed to touch.
EduVerse's OTP Incident
Your MERN course platform returns the OTP in plaintext in the API response. Razorpay payments are live. CORS is set to origin: true. This is a masterclass in how to ship a security audit finding as a feature.
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% weight60C
- Quality20% weight52D
- Depth15% weight55D
- Breadth10% weight65C
- Community10% weight50D
03 · Stats
365-day commit heatmap
158 active days
Language distribution
- Jupyter Notebook63%
- TypeScript12%
- JavaScript10%
- Go4%
- Python3%
- C++3%
- Other5%
04 · Numbers
Owned repos
non-fork
29
Commits
last 12 months
335
Followers
34
Joined GitHub
May 2020
05 · Top repos
Ankesh2004 /
GO-DFS
A zero-trust P2P distributed file system built from scratch in Go with end-to-end encryption, Kademlia DHT, and replication. Typed, documented, tested, but thin adoption (5 stars, no forks). Early-stage personal project demonstrating real systems knowledge.
Ankesh2004 /
PrioMon
Distributed gossip-protocol monitoring system with priority-based metric filtering. Early-stage research project with typed Python code, structured src/ and experiments/ layout, comprehensive README, and functional simulation framework using Docker and SQLite.
Ankesh2004 /
Chronous
A young distributed task scheduler in Go inspired by Slack's architecture, featuring Kafka → Redis → Worker pipeline with Consul locking and full LGTP observability stack. Shipped but minimal adoption (0 stars, 30 days old).
Ankesh2004 /
GA-Scheduler
C++17 genetic algorithm timetable scheduler with typed code, modular architecture, and JSON I/O. Personal project with solid fundamentals but no tests, CI, or adoption signals.
Ankesh2004 /
charya-hacksagon
Charya is a personal Windows activity tracker with SQLite storage, Flask dashboard, and optional encrypted S3 sync. Well-structured Python project with CLI/web interface, but very new (3 commits in 2 days), zero production adoption, and no tests despite HAS_TESTS=yes claim.
Ankesh2004 /
EduVerse
Full-stack MERN course platform with auth, payments (Razorpay), and file uploads. Has tests & basic structure, but lacks CI, typing, strong documentation, and contains security issues (plaintext OTP in responses, weak password validation, CORS origin: true).
Ankesh2004 /
csl
Brand-new (created 2026-04-20, last push same day) single-commit TeX/Python repo implementing a CSL sentence recognition pipeline with MediaPipe+Transformer+T5, well-documented via README but lacking tests, CI, license, and production maturity markers.
06 · Timeline
- May 20, 2020Joined GitHub
- Feb 22, 2024Created EduVerse
- Jun 26, 2025Created PrioMon
- Sep 29, 2025Created GA-Scheduler
- Nov 8, 2025Created GO-DFS — A robust zero-trust p2p distributed file storage system in Golang
- Mar 16, 2026Created Chronous
- Apr 3, 2026Created charya-hacksagon — A lightweight local personal memory assistant
- Apr 20, 2026Created csl
- Apr 20, 2026Most recent push to csl
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.