DEV Community


Posted on • Originally published at

Awesome Open Source Badges for your Git README

tl;dr Badges are a pretty way to display concise project information in a README.

Badges are a pretty way to display concise information about a project. They consist of a small image showing a topic and a status message and optionally linking to further information. Like tags they written in lowercase. Usually they are added to the top of a README file, which should contain sections for the topics anyway.

The most popular badge service is Shields. They allow custom badges and provide a huge list of dynamic badges. The later gather additional data from other services like code style checkers or download trackers. And a very big advantage is their »no tracking« policy.

In this post I will show a couple of badges you may consider adding to your Open Source package. The examples refer to GitHub and PHP/Packagist, but there are equivalents for most languages and plattforms.

Latest Version

Show the latest release of the package.

From GitHub tags:

[![Latest Version](<USER>/<REPOSITORY>?sort=semver&label=version)](<USER>/<REPOSITORY>/)

Latest Version

From Packagist tags:

[![Latest Version](<USER>/<PACKAGE>?label=version)](<USER>/<PACKAGE>/)

Latest Version

The link could point to a release page, Packagist or a Changelog file.


Show in which branch the development is done or how many commits since the latest release are added.


[![Development Branch](<DEVELOPMENT BRANCH>-green.svg)](<USER>/<REPOSITORY>/tree/<DEVELOPMENT BRANCH>/)

Development Branch

From GitHub release page:

[![Commits in development](<USER>/<REPOSITORY>/latest/)](<USER>/<REPOSITORY>/tree/<DEVELOPMENT BRANCH>/)

Commits in development

The link could point to the development branch or a milestone page.

Latest Build Status

Show the latest CI pipeline result.

From GitHub CI workflow:

[![Build Status](<USER>/<REPOSITORY>/<WORKFLOW>?label=build)](<USER>/<REPOSITORY>/actions)

Build Status

Programming language

Show the language which is used in the package.


[![Made With](](/docs/requirements/)

Made With

[![Made With](](/docs/requirements/)

Made With

The link could point to an installation guide or requirements section in your README.

Package Repository

Show where to get the package (Packagist, NPM, RubyGems etc).

This may be combined with the version badge. So this could show some statistics instead.

From Packagist:



From Packagist download counter:

[![Packagist Downloads](<USER>/<PACKAGE>.svg?label=packagist%20downloads)](<USER>/<PACKAGE>)

Packagist Downloads

Some package repositories support showing ratings instead. This is not possible for Packagist yet.


Documentation is key! Provide quick access to documentation.


[![Development Branch](<TYPE>-green.svg)](<USER>/<REPOSITORY>/blob/master/<DOC FILE>/)

Development Branch

From Read the Docs:

[![Documentation Status](<PROJECT>)](https://<PROJECT>

Documentation Status

Hint: A nice service is Inch CI, which measures how code is documented and shows the result in a badge. Currently supports JavaScript and Ruby only though.


Show the license of the package. This is crucial while researching compatible packages.


[![License](](<USER>/<REPOSITORY>/blob/master/<LICENSE FILE>)






From Packagist manifest:

[![License](<USER>/<PACKAGE>.svg)](<USER>/<REPOSITORY>/blob/master/<LICENSE FILE>)



A great part of Open Source is the possibility to let people contribute. Show contributers how to do so and add a link to a contribution guide.

Manual flags:

[![Contribution](](<USER>/<REPOSITORY>/blob/master/<CONTRIBUTION FILE>)


[![Contribution](](<USER>/<REPOSITORY>/blob/master/<CONTRIBUTION FILE>)


From GitHub contributors counter:



Another nice way to encourage contributions is the First Timers Friendly badge and a link to issues tagged with first-timers-only or contribute.

[![First Timers Friendly](](<USER>/<REPOSITORY>/labels/contribute)

First Timers Friendly

Code of Conduct

Show all contributors and maintainers of a project the common interest in an open and welcoming community.


[![Code of Conduct](🌐-ff69b4.svg?logoColor=white)](<USER>/<REPOSITORY>/blob/master/<CONTRIBUTION FILE>)

Code of Conduct

A popular code of conduct template is the Contributor Covenant.

[![Code of Conduct](](<CODE OF CONDUCT FILE>)

Code of Conduct


Show some metrics like security, dependencies, test coverage, code climate.


Provide a place where users may discuss how to use the package or fix issues.

A popular service is Gitter by GitLab. They provide a public chat for any repository. Users need no invitation link and dont need to sign up.



An alternative is a message board or linking to tags on Stack Overflow.


Show people how to they may support the project financially with donations, sponsorships or subscriptions.

GitHub allows to add several funding plattforms trough a FUNDING.yml.




From Liberapay:



From Open Collective:



<3 Open Source

Spread the love for Open Source.


[![Open Source Software](🤍-3DA639.svg)](

Open Source Software

Maybe you want to add a link to, a project which encourages users to send a simple “thank you“ note to creators of an Open Source package.

[![Say Thanks](](<USER>)

Say Thanks

Generic custom badges

If you want add any more information, then use a custom badge.



Overwrite dynamic badges

You may override the labels, colors and style of all badges by adding some parameter as described in the Shields documentation.

  • Change title: ?label=<TITLE>
  • Change color: ?color=<HEX>
  • Change style: ?style=flat-square
  • Add an icon from Simple Icons: ?logo=<NAME>

Top comments (0)