01 · Roasts
The 11-Minute Portfolio
GOOGLE_PLAYSTORE_DATA_ANALYSIS was born and died in 11 minutes across 3 commits. CUSTOMER_CHURN_ANALYSIS took 33 seconds. You're not doing data analysis — you're doing data speedruns.
Password: '12345'
Your ecommerce notebook has the password '12345' hardcoded, and crud-app has secret key 'secret123'. You built an *authentication* app with the digital equivalent of a sticky note on the monitor.
100% Jupyter, 0% Readme
Every byte in your public profile is a Jupyter Notebook, and 9 out of 11 repos have no README whatsoever. GitHub is not your personal NAS — other humans exist.
SQL Typo Bingo
SQL_PROJECT_DATA_CLEANING_AND_EDA has 'information_schemas', 'TABLE_SCHEMAS', 'laptops_backups', and 'select * from laptop' (missing the 's'). You wrote a data *cleaning* project with dirty data *and* dirty SQL.
Commit Velocity: Negative
61 commits in a year across 14 repos averages to 4.3 commits per repo. Your heatmap is 46 completely blank weeks out of 52. The grass on your contribution graph is not just dead — it was never planted.
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% weight18F
- Consistency20% weight55D
- Quality20% weight23F
- Depth15% weight30F
- Breadth10% weight30F
- Community10% weight25F
03 · Stats
365-day commit heatmap
12 active days
Language distribution
- Jupyter Notebook100%
- Python0%
- HTML0%
- CSS0%
04 · Numbers
Owned repos
non-fork
14
Commits
last 12 months
61
Followers
1
Joined GitHub
Sep 2025
05 · Top repos
priyanshu-pathak-555 /
VENDOR_PERFORMANCE_ANALYSIS
Personal data analysis project using Jupyter notebooks and SQLite to perform vendor performance analysis on beverage inventory, with basic ETL and statistical exploration but minimal documentation and no tests.
priyanshu-pathak-555 /
Hotel_booking_data_analysis
A personal data analysis project analyzing hotel booking cancellations using Jupyter notebooks. Demonstrates basic exploratory data analysis with matplotlib/seaborn visualizations, but lacks tests, CI, typed code, structured layout, and proper documentation for reproducibility. One-shot analysis effort.
priyanshu-pathak-555 /
crud-app
Beginner CRUD authentication tutorial project with Flask/SQLite. No tests, CI, or type hints. Basic app demonstrates password hashing and sessions but lacks polish and production readiness. Created and developed over 2 days with 16 commits.
priyanshu-pathak-555 /
MOVIE_RECOMMENDATION_SYSTEM
Personal educational project: Jupyter-based movie recommender with Streamlit frontend. No README, tests, CI, or license. Single-week development (4 commits in 15 days). Minimal scope and documentation.
priyanshu-pathak-555 /
data_validation_project
Personal data validation learning project with hardcoded paths, no tests, CI, or documentation. Implements basic PAN/email/numeric field validation on CSV data with minimal scope and no reusability.
priyanshu-pathak-555 /
ECOMERCE_DATA_ANALYSIS_USING_PANDAS_SQL
Single-day learning project: Jupyter notebook with 6 basic SQL queries on ecommerce data plus a CSV-to-SQL loader script. No tests, CI, documentation, or version control discipline. Credentials hardcoded and requires manual setup.
priyanshu-pathak-555 /
ML_MODEL1
Minimal handwritten digit recognition project using kNN with Streamlit UI. No docs, tests, CI, or version control hygiene. Single-push experiment with basic implementation.
priyanshu-pathak-555 /
SQL_PROJECT_DATA_CLEANING_AND_EDA
Bare SQL learning exercise with two unpolished scripts for laptop data cleaning/EDA. Zero ecosystem presence, no documentation, structure, tests, or CI. Minimal commit activity and completely isolate, unexported work.
priyanshu-pathak-555 /
CUSTOMER_CHURN_ANALYSIS
Single Jupyter notebook with basic exploratory data analysis on customer churn dataset; no README, no tests, no documentation, one commit in under 1 minute.
priyanshu-pathak-555 /
IMAGE_CAPTION_GENERATOR
Minimal Streamlit app for image captioning with no README, no tests, no CI, and only a single recent commit. Lacks documentation, project structure, and meaningful git history. Appears to be a one-off experiment or homework submission.
priyanshu-pathak-555 /
GOOGLE_PLAYSTORE_DATA_ANALYSIS
Minimal data analysis notebook dump with zero stars, no README, no documentation, no tests, and only 3 commits over 11 minutes. Created and abandoned immediately; shows no sustained work or architectural intent.
06 · Timeline
- Sep 25, 2025Joined GitHub
- Oct 15, 2025Created Hotel_booking_data_analysis
- Oct 15, 2025Created VENDOR_PERFORMANCE_ANALYSIS
- Mar 29, 2026Created ML_MODEL1
- Apr 4, 2026Created crud-app
- Apr 13, 2026Created IMAGE_CAPTION_GENERATOR
- Apr 13, 2026Created MOVIE_RECOMMENDATION_SYSTEM
- Apr 14, 2026Created CUSTOMER_CHURN_ANALYSIS
- Apr 14, 2026Created ECOMERCE_DATA_ANALYSIS_USING_PANDAS_SQL
- Apr 14, 2026Created GOOGLE_PLAYSTORE_DATA_ANALYSIS
- Apr 25, 2026Created data_validation_project
- Apr 25, 2026Created SQL_PROJECT_DATA_CLEANING_AND_EDA
- Apr 28, 2026Most recent push to MOVIE_RECOMMENDATION_SYSTEM
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.