GitGaze

GitGaze

Your GitHub, Reimagined with GitGazeGitGaze 🔮

5 followers

Showcase your GitHub statistics and activities in a personalised and share-ready dashboard.
GitGaze gallery image
GitGaze gallery image
Free
Launch Team
Framer
Framer
Launch websites with enterprise needs at startup speeds.
Promoted

What do you think? …

Atharv Vani
Maker
📌
🚀 Why I built GitGaze & What inspired me: 1. GitHub profiles are powerful, but not always recruiter-friendly. 2. I noticed recruiters and founders often skim profiles and miss real impact because data is scattered across repos, graphs, and tabs. 3. I wanted a single, clean view that instantly tells a developer’s story — something you can confidently share instead of saying “check my GitHub”. That’s how GitGaze was born: a visual, share-ready GitHub dashboard. 🧩 What problems GitGaze solves? 1. No more scrolling endlessly through repositories 2. No more guessing impact from raw commit graphs 3. No more sharing cluttered profile URLs 🔮 GitGaze gives you: 1. A clean bento-style dashboard with key insights at a glance 2. Clear visibility into contributions, streaks, top languages, active months 3. A GitHub Wrapped–style experience that tells your yearly story 4. A single sharable link that recruiters can understand in seconds GitGaze is still evolving, and I’ll be sharing each feature and improvement regularly here. Would love your feedback, ideas, or even feature requests 🙌 Let’s make GitHub profiles easier to understand 🚀
Jacey

@atharv_110 Upvoted — this is the kind of “GitHub, but recruiter-friendly” I wish existed when sending my profile around. The bento layout + GitHub Wrapped vibe is super clean. How do you handle private repos/org contributions, and can I customize what shows (top projects, pinned highlights)? Would love to share a link in my portfolio.

Atharv Vani

@hijacey As of now there’s no support of private or org repo as gitgaze do not require any sign in or sign up but yes the contribution counts in private repos are publicly available so used that.

This requirement will be addressed in future releases.

Thanks for the valuable words and support! 😊