I Built an AI Tool That Analyzes GitHub Profiles & Developer Portfolios

Najmul Hasan — Thu, 09 Apr 2026 23:32:29 +0000

I built an AI tool that analyzes your GitHub & portfolio like a recruiter.

Most developers think their GitHub profile is “fine”.

It has repos.

It has commits.

Maybe even some stars.

But when someone actually reviews it — especially a recruiter — the experience is very different.

They’re not counting commits.
They’re scanning for signal.

And most profiles don’t communicate it clearly.

The problem

A GitHub profile is supposed to represent your work.

But in reality:

Important projects are buried
READMEs are incomplete or unclear
Contribution activity looks inconsistent
Tech stack is hard to understand at a glance
Portfolio sites look good but say very little

From the outside, it’s hard to quickly answer:

“Is this developer actually strong?”

And from the developer side, it’s even harder to see your own blind spots.

So I built something to solve this

I built Devfolio Analyzer — a tool that evaluates GitHub profiles and developer portfolios and turns them into a structured, readable signal.

👉 Live: https://devfolioanalyzer.vercel.app
👉 Docs: https://devfoliodocs.vercel.app

The goal is simple:

Show how your profile actually reads to someone else.

What it does

You enter a GitHub username.

The system:

Fetches public GitHub data
Extracts meaningful signals
Normalizes them into structured data
Runs an AI-based evaluation
Returns a scored report with feedback

What it evaluates

Instead of vanity metrics, it focuses on five core areas:

1. Project quality

README clarity
Repo structure
Presence of tests
CI/CD setup
Commit quality

2. Tech stack signal

Languages used
Framework detection
Recency of technologies

3. Contribution consistency

Activity patterns
Streaks and gaps
Recent momentum

4. Portfolio presentation

Profile README
Pinned repos
Bio and links
Overall clarity

5. Community engagement

PRs to external repos
Issue activity
Open-source participation

Example output

Instead of vague feedback, you get something like:

Score: 78 / 100
Label: Good

Issues:

Inconsistent recent activity
Weak README structure in top repos
Profile presentation not aligned with project quality

Suggestions:

Improve top repo documentation
Add clearer profile messaging
Reorganize pinned repositories

Why this matters

Most developers optimize the wrong things:

stars
repo count
follower numbers

But those don’t tell the full story.

What actually matters:

clarity
consistency
presentation
real project quality

Because that’s what people look for when they evaluate you.

How it’s built (quick overview)

Frontend: Next.js + Tailwind
Backend: API routes
Data: GitHub REST API
AI: LLM-based scoring pipeline
Cache: Redis (Upstash)
Deployment: Vercel

Everything runs serverless — no separate backend needed.

Some limitations (important)

This isn’t magic.

Only public GitHub data is analyzed
Private work is invisible
LLM scoring has small variations
Code quality is inferred, not executed

The goal is not perfection — it’s clarity.

What I learned building this

Two things stood out:

1. Most profiles are harder to read than people think

Even strong developers often have weak presentation.

2. Signal is different from activity

You can be active and still look unclear.
You can have fewer repos and look stronger.

If you want to try it

👉 LINK

Run your profile through it and see what shows up.

You’ll probably notice things you didn’t expect.

I’d really like feedback

If you try it, I’d love to know:

Does the score feel fair?
Is the feedback actually useful?
What feels missing or inaccurate?

This is still evolving, and real feedback matters more than assumptions.

Final thought

Your GitHub profile is more than a code dump.

It’s how your work is interpreted.

And small improvements there can make a big difference.

DEV Community: Najmul Hasan