Transformez votre profil GitHub en CV

resumefromgit.com is a free GitHub profile analyzer and CV generator. Give it a public GitHub username and it reads that account’s public data - repositories, languages, stars, followers and a year of contribution history - through GitHub’s own public API, then renders it as a visual developer dashboard and an ATS-friendly PDF resume.

There is no login, no GitHub OAuth authorization, and no AI anywhere in the pipeline. Every number on the page is pulled directly from GitHub and computed with plain arithmetic, not summarized or rewritten by a model. The result is a permanent, shareable profile page at resumefromgit.com/username that works as a developer portfolio link, and a downloadable resume built from the same data.

GitHub contribution calendar and contribution history

The contribution calendar renders a full year of public activity as the same green-square heatmap GitHub shows on a profile, plus the totals behind it: current streak, longest streak and busiest day of the week. It is a fast way to see whether someone codes in short bursts around deadlines or keeps a steady weekly rhythm - context a raw commit count alone does not give you. We wrote up exactly what the graph counts and what it leaves out in a separate guide on how the GitHub contribution graph works.

GitHub repository analytics

Every public repository is ranked by stars, forks and recent activity, then summarized into the metrics recruiters actually scan for: total repositories, total stars earned, and the handful of projects that represent someone’s best public work. Instead of paging through a repository list on GitHub itself, you get the same information as one readable table.

Programming language and tech stack breakdown

resumefromgit.com aggregates language bytes across every public repository and renders the split as a donut chart and a ranked list - not just “knows JavaScript,” but roughly how much of someone’s public code is JavaScript versus Python versus Go. Paired with repository topics, it doubles as a tech-stack summary: the frameworks and runtimes a developer actually reaches for.

Achievements and open source activity

The dashboard lists any achievement badges GitHub has awarded and a breakdown of open-source activity - pull requests opened, issues filed, and contributions to repositories the person does not own. This is often the most convincing section for open-source contributors, since it separates “wrote code for their own projects” from “shipped changes other maintainers accepted.”

A developer timeline built from real activity

Account creation date, first commits and shifts in primary language over time are plotted as a timeline - a rough but honest picture of how someone’s public work has evolved. It will not replace a real work history, but it shows trajectory: whether someone has been building consistently for years or picked up GitHub recently.

A downloadable, ATS-friendly PDF resume

Every profile includes a free resume builder. It pre-fills your GitHub data - name, bio, top projects, language skills - and lets you add what GitHub does not publish: work experience, education and a summary. The PDF uses a single-column, plain-text layout based on the widely used Jake’s Resume format, with no tables, text boxes or multi-column sections that trip up applicant tracking systems. Everything you type is stored in your browser’s localStorage, not on our servers, and the PDF is generated client-side.

A permanent, public GitHub profile page

Every generated dashboard lives at a stable URL - resumefromgit.com/username - that you can put in a bio, a job application or an email signature. It refreshes from live GitHub data on a twelve-hour cache, so it stays current without you doing anything, and it costs nothing to keep online.

A resume describes what you say you did. A GitHub CV shows the actual commits, pull requests and shipped projects behind those claims - evidence a hiring manager can click into and verify in under a minute. For roles where code quality matters - software engineering, DevOps, data and AI roles - that verifiability is worth more than another adjective on a resume.

It also solves a logistics problem: most developers do not have time to manually screenshot repositories, tally stars, or write up a project list every time they apply somewhere. resumefromgit.com generates that summary in the time it takes to type a username.

GitHub CV vs. writing a resume by hand

Building the same summary manually means opening each repository, counting stars and forks, guessing at a language split, and formatting a PDF that will not break when it is parsed by Workday or Greenhouse - typically an hour or more of work, redone every time a project changes.

resumefromgit.com does the same job from GitHub’s public API in the time it takes the page to load, and updates automatically the next time anyone views it. What it will not do is replace judgment: it cannot explain why you made an architectural decision, describe a private-repo project, or say how you work with a team. Use it for the parts that are objectively true - activity, languages, project scale - and write the parts that need a human voice yourself.

Why recruiters and hiring managers trust GitHub profiles

GitHub is one of the few parts of a developer’s application that is not self-reported. A recruiter can open a candidate’s profile and see, unfiltered, how often they commit, whether their code has tests, and whether other engineers have merged their pull requests. That is why technical recruiters routinely ask for a GitHub link alongside - or instead of - a cover letter, and why a thin, empty-looking profile can undercut an otherwise strong resume. resumefromgit.com does not change what is on your GitHub; it just makes it faster for someone to read.

What makes a resume truly ATS-friendly

Applicant tracking systems parse resumes as plain text, extracting fields like name, dates and skills. Elements that look fine to a human - text inside a table cell, a two-column layout, a skills graphic, a header or footer - frequently parse as garbled text or get dropped entirely, which can knock a qualified candidate out before a person ever opens the file.

The PDF resumefromgit.com generates avoids all of that by design: single column, real selectable text rather than an image, standard section headings, and no graphical elements carrying information. You can select and copy every line of it in a PDF reader, which is a quick way to check whether any resume - from this tool or anywhere else - will parse cleanly.

Common mistakes developers make with their GitHub profile

A few patterns show up repeatedly on profiles that undersell real work:

• Pinning forked or tutorial-following repositories instead of original projects.
• Leaving every repository without a README, so a visitor cannot tell what a project does without reading the code.
• A photo-less, bio-less account, which reads as inactive even when the commit history is not.
• No public organization or pull-request activity, even when most of the real work happens in private company repositories - worth noting explicitly rather than leaving a recruiter to guess.
• A default, un-customized profile README, missing an easy chance to add context GitHub’s raw activity cannot show.

None of these are difficult to fix, and the dashboard makes them easy to spot at a glance - an empty language chart or a flat contribution graph stands out immediately.

Profile data comes from a single GraphQL query to GitHub’s public API, made server-side and cached for up to twelve hours. That request uses a read-only server credential that can only see what is already public - it cannot read private repositories, and it is never used to act on your account. Because the query runs once per profile per cache window rather than on every page view, the site stays fast without hammering GitHub’s rate limits.

Privacy: what we store, and what we never ask for

You are never asked to sign in with GitHub, grant an OAuth permission, or hand over an access token. The only data this site holds is a short-lived cache of what GitHub already publishes, plus any resume fields you type - which stay in your browser’s localStorage and are never uploaded to our servers. Read the full privacy policy for specifics on caching, analytics and cookies.