01 · Roasts
Commit confetti cannon
656 yearly commits and 171 multi-repo volume say you ship constantly; tests and CI missed the invite on nearly every repo.
One-star constellation
12 scored repositories account for 15 total stars and 0 forks—lots of launches, almost no orbital pull.
Single-file boss rush
Ramp-Monopoly, DigitalClock, and Ramp-Website-New put serious ambition into index.html, then leave architecture in the loading screen.
Chatbot multiverse
RampageBot, jerechat, and RampChat give you three routes to conversational AI; automated regression coverage gives you zero.
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% weight68C
- Consistency20% weight65C
- Quality20% weight38F
- Depth15% weight58D
- Breadth10% weight55D
- Community10% weight25F
03 · Stats
365-day commit heatmap
172 active days
Language distribution
- Python50%
- HTML44%
- C++4%
- Rust1%
- CSS0%
- Other1%
04 · Numbers
Owned repos
non-fork
15
Commits
last 12 months
656
Followers
6
Joined GitHub
Mar 2025
05 · Top repos
Jeremy-Qian /
RampageBot
A small deployed Streamlit chatbot for The Rampage, using NLTK preprocessing and scikit-learn TF-IDF similarity, with a named public domain but limited adoption and no testing or CI.
Jeremy-Qian /
Hangman
A small, documented Rust CLI Hangman game with basic modular functions and random word selection; it has MIT licensing and GitHub Actions automation, but little adoption and limited project scope.
Jeremy-Qian /
jerechat
A documented Streamlit chatbot with PyTorch response generation, invitation access, Supabase feedback, and A/B model comparison; it is a small 1-star project without tests or CI.
Jeremy-Qian /
HitTheGiant
A documented but small C++ terminal game with two modes, randomized giants, inventory, rewards, and a single-file implementation; it lacks tests, CI, and a license.
Jeremy-Qian /
DigitalClock
A small, deployed fullscreen clock with configurable visual controls and Wikimedia background search, but adoption and engineering scope remain limited.
Jeremy-Qian /
Ramp-Monopoly
A small, playable two-player Monopoly web game implemented in a single index.html, with canvas board rendering, dice, properties, money, turns, and themed UI, but limited documentation and engineering safeguards.
Jeremy-Qian /
rampwebsite
A small Streamlit website with navigation, informational pages, a local-storage poll demo, and a bundled Tkinter sample app; it is documented but lacks adoption signals, tests, CI, and production backend integration.
Jeremy-Qian /
20-Questions
A functional MIT-licensed Python CLI Twenty Questions game in main.py, with JSON-backed learning and a clear README, but no tests, CI, or typed structure and minimal demonstrated adoption.
Jeremy-Qian /
jeremy-qian.github.io
A small, polished personal portfolio site with a focused HTML/CSS implementation, three linked projects, and minimal repository infrastructure or adoption.
Jeremy-Qian /
RampChat
Small Streamlit/Supabase group-chat template with login, avatars, message persistence, and theming, but it is explicitly experimental and its database is shut down.
Jeremy-Qian /
Jeremy-Qian
A personal GitHub profile configuration repository with a styled README and identity badges, but no source files, tests, CI, license, or demonstrated external adoption.
Jeremy-Qian /
Ramp-Website-New
A small, documented MIT-licensed HTML redirect page with a polished loading animation and fallback links, but no tests, CI, typed code, or evidence of meaningful external adoption.
06 · Timeline
- Mar 8, 2025Joined GitHub
- Mar 8, 2025Created rampwebsite — Ramp website
- Mar 17, 2025Created HitTheGiant — A C++ Game that.. lets you hit giants.
- May 10, 2025Created Jeremy-Qian — Config files for my GitHub profile.
- Oct 11, 2025Created Ramp-Website-New — Nothing. redirects to the-rampage.weebly.com
- Nov 17, 2025Created Ramp-Monopoly — A Ramp-themed Monopoly Game.
- Nov 17, 2025Created jeremy-qian.github.io — Personal website, of course.
- Nov 17, 2025Created jerechat — JereChat, just a chatbot.
- Dec 17, 2025Created 20-Questions — A simple Twenty Questions game, with Rampions.
- Mar 2, 2026Created RampChat — Template for hosting your own streamlit social media server.
- May 13, 2026Created RampageBot — Science Fair Project. Integrated at rampage.is-great.org
- Jun 28, 2026Created Hangman — A simple hangman game in Rust.
- Aug 3, 2026Created DigitalClock — Because the digital clocks online are paid and are bad, I decided to make one myself. CAUTION- Completely dominated by AI code.
- Aug 28, 2026Most recent push to DigitalClock
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.