▸ This tool was built by an AI agent from Zoral
← RATE MY GITHUB

#375 — Top 78.4%

Peddinti-Sriram-Bharadwaj

Sriram Bharadwaj

C

Getting there

Overall

0.0

/ 100

01 · Roasts

Portfolio, not pull requests

103 public repos and 130 recent sampled commits make the output real; 3 total stars mean the audience has not arrived yet.

Research lab speedrun

SOR_thesis_code schedules 360 runs and 11 Atari games, yet the test suite is still an imaginary control group.

CI is a rare species

Only the profile repo shows CI; random-experiments, MCTS, dormat_RL, and SOR_thesis_code all ship without it.

Burst-mode builder

MCTS packed 30 sampled commits into Aug 11–14, while Reward-Design-Agent packed 13 into a day. Sustained polish wants a turn.

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

  • Impact
    25% weight
    56D
  • Consistency
    20% weight
    65C
  • Quality
    20% weight
    52D
  • Depth
    15% weight
    58D
  • Breadth
    10% weight
    55D
  • Community
    10% weight
    50D

03 · Stats

365-day commit heatmap

43 active days

Less
More

Language distribution

7 langs
  • Python66%
  • C++11%
  • Kotlin10%
  • Java6%
  • JavaScript4%
  • HTML1%
  • Other2%

04 · Numbers

Owned repos

non-fork

67

Commits

last 12 months

158

Followers

20

Joined GitHub

Oct 2021

05 · Top repos

Peddinti-Sriram-Bharadwaj /

random-experiments

43/100

A zero-star experimental monorepo containing a saddle-point optimization demo plus three substantial Android/on-device ML experiments, with useful per-project READMEs but no visible test, CI, license, or adoption signals.

I25Q55D50
READMETyped
Kotlin013d ago

Peddinti-Sriram-Bharadwaj /

MCTS

35/100

A substantial three-track MCTS/AlphaZero Python suite spanning classical games, JAX/Flax self-play, TD-SOR training, and hardware profiling, but it has no observed adoption and was built in a short burst.

I20Q45D35
README
Python01mo ago

Peddinti-Sriram-Bharadwaj /

dormat_RL

34/100

A substantial documented PyTorch RL research repository implementing dormant-neuron recycling, multi-head controls, Atari dormancy analysis, and neuron-level circuit experiments, but with no demonstrated adoption, tests, CI, license, or typed Python.

I20Q45D35
README
Python016d ago

Peddinti-Sriram-Bharadwaj /

SOR_thesis_code

34/100

A documented, multi-module Python research codebase implementing SOR-enhanced DQN experiments across LunarLander and Atari, with reproducibility and distributed Optuna tooling but no tests, CI, license, or demonstrated adoption.

I20Q45D35
README
Python01mo ago

Peddinti-Sriram-Bharadwaj /

Peddinti-Sriram-Bharadwaj

30/100

A maintained GitHub profile repository with a substantial research-oriented README and one scheduled blog-update workflow, but no shipped source product, tests, license, or meaningful adoption signals.

I20Q38D45
READMECI
Unknown017d ago

Peddinti-Sriram-Bharadwaj /

Reward-Design-Agent

29/100

A documented, modular Python prototype for multimodal Gemini reward design with PPO, video feedback, memory tracking, benchmarking, and SLURM support, but it has 0 stars, no tests or CI, no license, and only a one-day history.

I20Q42D25
README
Python026d ago

Peddinti-Sriram-Bharadwaj /

qwen_self_play

27/100

A documented research prototype for Qwen self-play PPO on Tic-Tac-Toe, with modular environment, agent, trajectory collection, and TRL trainer code, but no tests, CI, license, or demonstrated adoption.

I20Q40D20
README
Python017d ago

Peddinti-Sriram-Bharadwaj /

RL_practice

5/100

RL_practice is an empty practice scaffold containing only a minimal README and no implementation, tests, CI, license, or typed source.

I5Q10D5
README
Unknown026d ago

06 · Timeline

  1. Oct 12, 2021
    Joined GitHub
  2. May 8, 2022
    Created Peddinti-Sriram-Bharadwaj — Config files for my GitHub profile.
  3. Jun 2, 2026
    Created SOR_thesis_code
  4. Aug 11, 2026
    Created MCTS
  5. Aug 24, 2026
    Created Reward-Design-Agent
  6. Aug 25, 2026
    Created RL_practice — practice repo
  7. Aug 25, 2026
    Created qwen_self_play
  8. Aug 26, 2026
    Created dormat_RL
  9. Aug 28, 2026
    Created random-experiments — collection of some small random experiments.
  10. Sep 7, 2026
    Most recent push to random-experiments

07 · Compare

github.com/
Peddinti-Sriram-Bharadwaj · 6dmedian coder

08 · Rubric

How this score was produced

Overall = Σ (category × weight) + gentle top-end curve

CategoryWeightScoreContrib.
Raw total56.6
Top-end curve+4.1
Final overall60.7

Tier thresholds

S90100Mass-producing humansA8089Ship machineB7079Solid engineerC6069Getting thereD4059README enthusiastF039GitHub tourist
▸ How the pipeline works
  1. 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.
  2. 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
  3. 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.
  4. 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.
  5. 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.
Peddinti-Sriram-Bharadwaj · 60.7/100 — Rate My GitHub