What the Active Developer Badge Is and Who Can Get It
GitHub's Active Developer Badge is a visual marker on your profile that shows you have made contributions to open source repositories in the past year. It appears as a small badge next to your name and profile picture. The badge is not something you request or explore for — GitHub awards it automatically to accounts that meet the contribution threshold.
The badge recognizes sustained participation in the open source community. It does not require you to be famous, to have written perfect code, or to maintain your own popular project. You earn it by making contributions that GitHub's system can count and verify.
Key Takeaways
- The Active Developer Badge appears automatically on your GitHub profile when you have made contributions in at least four of the past twelve months.
- Contributions include pull requests, issues, code reviews, and commits to public repositories — not just your own projects.
- Your contributions must be visible in your public activity graph; private repositories and contributions do not count toward the badge.
- The badge updates once per day, so changes to your contribution history may take up to 24 hours to appear on your profile.
- You can check your contribution count and activity timeline on your GitHub profile under the "Contributions" section to see your progress toward the badge.
What Counts as a Contribution for the Badge
GitHub counts several types of activity toward the Active Developer Badge. A pull request counts when you submit code changes to a public repository, whether to a project you own or one maintained by someone else. A commit counts when your code is merged into the default branch of a public repository. Issues count when you open or comment on them in public repositories. Code reviews count when you review pull requests submitted by others.
The key requirement is that the activity must be visible in a public repository. If you push code to a private repository, contribute to a private fork, or work on code that is not yet merged, those actions do not count toward the badge. Similarly, contributions to repositories you have deleted no longer count, even if you made them when the repository existed.
Contributions must also be attributed to your GitHub account. If you commit code using a different email address or name, or if you contribute under a different account, that activity will not appear on your profile unless you connect those identities to your main account through GitHub's email settings.
The Contribution Timeline and How the Badge Updates
The Active Developer Badge requires contributions spread across at least four different months within the past twelve months. This means you cannot earn the badge by making all your contributions in a single month, even if you make hundreds of commits. GitHub looks at the calendar months in which you had at least one contribution, not the total number of contributions.
For example, if you contributed in January, March, July, and November of the past year, you meet the four-month requirement. If you contributed every single day in January and February but nothing since, you do not yet may have access to. The badge updates once per day, usually in the early morning hours UTC. If you make a contribution today, it may take up to 24 hours to appear in your contribution graph and affect your badge status.
How to Check Your Contribution Count and Activity
Visit your GitHub profile by clicking your profile picture in the top right corner and selecting "Your profile." On your profile page, you will see a section labeled "Contributions" with a graph showing your activity over the past year. This graph displays a grid of small squares, each representing one day. Darker squares indicate days with more contributions; lighter or empty squares indicate days with no contributions.
Below the graph, GitHub displays your total contribution count for the past year. Hover over any square in the graph to see the exact number of contributions on that day. You can also click on individual months to see which days you contributed and what types of contributions they were. If you do not see the Active Developer Badge on your profile yet, check whether your contributions span at least four different months. If they do, wait up to 24 hours for the badge to appear.
You can also view your contribution activity on other people's profiles in the same way. This helps you understand what counts as a contribution and see examples of sustained activity over time.
How to Build Contributions Across Multiple Months
The most straightforward path to the Active Developer Badge is to contribute to open source projects regularly. Start by finding repositories that interest you. GitHub's Explore page suggests projects based on your interests and experience level. Look for repositories with labels like "good first issue" or "help wanted" — these are typically maintained by developers who welcome new contributors.
You do not need to contribute to the same project every month. You can contribute to different projects in different months, and each contribution counts toward your four-month requirement. Some people contribute to projects they use, others fix bugs in libraries they depend on, and others help with documentation or testing. The type of contribution matters less than the consistency of showing up across multiple months.
If you maintain your own open source project, contributions to your own repositories count toward the badge just as much as contributions to other people's projects. You can also earn contributions by reviewing pull requests from other developers, opening issues to report bugs or suggest features, or improving documentation.
Why Your Badge Might Not Appear Even With Contributions
If you have contributions in four or more months but do not see the badge, check a few common issues. First, verify that your contributions are in public repositories. Contributions to private repositories, even if they are your own, do not count. Second, check that your contributions are attributed to your current GitHub account. If you used a different email address when committing code, those commits may not appear on your profile. You can add email addresses to your GitHub account in your email settings to claim past contributions.
Third, confirm that your profile is not set to private. If you have hidden your activity from public view, the badge will not appear. You can check this in your profile settings under "Public profile." Fourth, wait at least 24 hours after your fourth contribution month begins. The badge does not appear when ready; GitHub updates it once per day.
If you have checked all of these and still do not see the badge, your contributions may not yet span four full calendar months. Remember that GitHub counts calendar months, not rolling 30-day periods. If you contributed in January, February, and March, you need at least one more contribution in a fourth month — April, May, June, or later — to may have access to.
Maintaining Your Badge Over Time
Once you earn the Active Developer Badge, it remains on your profile as long as you continue to meet the requirement: at least one contribution in four different months within the past twelve months. This means you do not need to contribute every month, only that you have activity spread across at least four months in any rolling twelve-month window.
If you stop contributing entirely for more than eight months, you will eventually lose the badge. For example, if your last contribution was in January and it is now October, and you have not contributed since January, the badge will disappear because you no longer have contributions in four different months within the past year. To keep the badge, make at least one contribution every few months in different months.
Frequently Asked Questions
Do contributions to my own repositories count toward the badge?
Yes. Contributions to repositories you own count the same as contributions to other people's projects. Commits, pull requests, issues, and code reviews on your own public repositories all count toward the Active Developer Badge.
What if I contributed a lot in one month but nothing since?
A single month of high activity does not earn the badge. You need contributions in at least four different calendar months within the past year, regardless of how many contributions you made in each month. One contribution per month across four months qualifies; one hundred contributions in one month does not.
Can I earn the badge with contributions to documentation or non-code projects?
Yes. Pull requests and commits to documentation, README files, and other non-code content count as contributions. You can also earn the badge by opening and commenting on issues, which does not require writing code at all.
How long does it take for the badge to appear after I meet the requirements?
GitHub updates the badge once per day, usually in the early morning UTC. If you meet the four-month requirement today, the badge may take up to 24 hours to appear on your profile. Check back the next day if you do not see it when ready.
Will the badge disappear if I stop contributing?
Yes. The badge requires contributions in at least four months within the past twelve months. If you stop contributing and more than eight months pass without activity, you will eventually lose the badge because your contributions will no longer span four months in the rolling twelve-month window.