Your open-source identity, beyond GitHub.
OSSfolio is participating in EluSoC Season 1 2026. If you are here through EluSoC, welcome! Read through this README and then check out CONTRIBUTING.md to get started.
GitHub shows your repos. OSSfolio shows you.
OSSfolio is a free, open-source platform where every contributor gets a public profile page at https://ossfolio.qzz.io//username — showcasing the full picture of their open-source journey. The PRs you merged into other projects, the issues you filed, the orgs you contributed to, the programs you participated in like GSoC or GSSoC — all in one shareable link.
No manual input. Just sign in with GitHub and your profile is ready.
GitHub profiles are built around repositories — stars, forks, and commit graphs tell only part of the story.
If you have spent months reviewing PRs, triaging issues, contributing to other people's projects, or participating in GSoC/GSSoC — none of that shows up clearly on your GitHub profile. Recruiters miss it. Maintainers miss it. You cannot share it.
OSSfolio is built to fix that — for students applying to GSoC, for developers sharing their work with recruiters, and for anyone who wants their contributions to actually be seen.
- Shareable profile at
https://ossfolio.qzz.io//username - Contribution stats — merged PRs, issues opened, commits, reviews
- Heatmap and streak — visualise your activity across the year
- Tech stack — auto-detected from your repos, no tagging needed
- Organizations — every org you have contributed to
- GSoC / GSSoC badges — show your program participation
- Contributor score — a single number summarising your impact
- Leaderboard — see how you rank against other contributors
OSSfolio calculates a contributor score to provide a quick summary of a developer's open-source activity.
The score combines different types of contributions across GitHub and assigns a weight to each activity type. Higher scores generally indicate more contribution activity, but the score should be viewed as a summary rather than a measure of skill or developer quality.
| Activity | Weight |
|---|---|
| Commits | 1 point each |
| Pull Requests | 3 points each |
| Issues | 2 points each |
| Reviews | 2 points each |
| Repository Stars | 0.1 point each (capped at 1000 stars) |
The score is designed to capture a mix of:
- Code contributions through commits
- Collaboration through pull requests and reviews
- Community participation through issues
- Project impact through repository stars
The contributor score is not a ranking system and should not be treated as a definitive measure of developer skill, experience, or value.
It is simply a lightweight summary of publicly visible open-source activity.
Contributors who want to understand the exact implementation can review:
src/lib/score.ts
| Layer | Tech |
|---|---|
| Frontend | Next.js · TypeScript · Tailwind CSS · shadcn/ui · Framer Motion |
| Backend | Supabase · PostgreSQL |
| Data | GitHub GraphQL API |
| Hosting | Cloudflare Pages |
What you need before starting:
- Node.js 20+
- A free Supabase account
- Git
Steps:
# 1. Fork the repo on GitHub, then clone your fork
git clone https://github.com/<your-username>/ossfolio.git
cd ossfolio
# 2. Install dependencies
npm install
# 3. Copy the environment variables file
cp .env.example .env.localSetting up the database (pick one):
Option A — Supabase Dashboard (recommended for most contributors, no extra tools needed)
- Create a free project at supabase.com
- Go to your project → SQL Editor → New query
- Copy the contents of
supabase/schema.sql→ paste → click Run- All tables and permissions are created instantly
Option B — Supabase CLI (if you prefer local development with Docker)
npm install -g supabase supabase start # starts a local Supabase instance supabase db reset # creates all tables + loads sample data
Finishing up:
Once Supabase is set up, copy your project URL and anon key into .env.local (you will find them in your Supabase dashboard under Project Settings → API), then:
npm run devOpen http://localhost:3000 and you are in.
For a detailed walkthrough — environment variables, GitHub OAuth setup, database change guidelines — see CONTRIBUTING.md.
OSSfolio is built by contributors, for contributors. That is kind of the whole point.
Before you start:
- Read CONTRIBUTING.md — it covers setup, rules, and what we expect
- Read CODE_OF_CONDUCT.md — short and worth it
How to get started:
- Browse open issues — filter by
good first issueif it is your first time - Comment on the issue with your approach, written in your own words
- Wait to be assigned before you start working
- Open your PR once assigned, fill out the template fully
A few things to keep in mind:
- Do not submit a PR without being assigned to the issue first
- Once you submit a PR, it will be reviewed within 12 hours. Please be patient and avoid pinging repeatedly before that time
- If you used AI to help write code, mention it in the PR and make sure you actually understand everything you changed
- If you have doubts, you can reach out on LinkedIn — send one message and give some time for a response
ossfolio/
├── src/
│ ├── app/ # Next.js app router pages and API routes
│ ├── components/ # Reusable UI components
│ │ ├── ui/ # Base shadcn/ui components
│ │ ├── home/ # Landing page sections
│ │ ├── layout/ # Header, footer, navigation
│ │ └── profile/ # Profile page components
│ ├── lib/ # Utilities, helpers, API clients
│ └── types/ # TypeScript type definitions
├── supabase/
│ ├── migrations/ # Database migration files (one per schema change)
│ ├── schema.sql # Full schema for dashboard setup
│ └── seed.sql # Sample data for local development
└── public/ # Static assets
Everyone who has helped build OSSfolio — code, design, docs, ideas, all of it.
MIT — free to use, fork, and build on.