Repo Badges Save

:star: Use repo badges (build passing, coverage, etc) in your readme/markdown file to signal code quality in a project.

Project README

Code Repository Badges

build passing

Why? start with why

As people who are passionate about writing great code we display "badges" in our code repositories to signal to fellow developers that we set ourselves high standards1 for the code we write, think of them as the software-equivalent of the brand on your jeans or other reliable product.


We use the following badges (listed in order of importance):

  • Documentation - Inline docs most people don't think of documentation as the "priority" for their (technical) project, instead people focus on solving the problem challenge e.g. by writing some code, and if it works, they add a TODO to "improve the docs" ... It may initially be counter-intuitive to think of Documentation as being the highest priority or first activity in a technical project but there are several reasons why it is:

    • Clearly setting out your own understanding of "the challenge" and then formulating a Question to be answered is the basis for "The Scientific Method". Without it you are like a blind-folded camel in the desert; unlikely to go straight to the oasis!
    • Describing your "success factors" or "acceptance criteria" before you start so you know when you've achieved your goal!
    • Communicating with current collaborators what problem you are/were trying to solve.
    • Making it immediately clear to everyone if you have succeeded in solving the challenge
    • Saves time in the short-run because you are immediately focused on the challenge and don't waste time on distractions.
  • Security - Known Vulnerabilities - Snyk Dependency Security Vulnerability Checking for your project: is a free service provided by the lovely people at Snyk that checks if any of your dependencies have a security vulnerability. This badge is a great way to reassure people using your app/site that security is being checked.

Top tip: Guy Podjarny @guypod the founder of Snyk hosts "The Secure Developer" Podcast.
It's a "must" for all devs! Subscribe if you aren't already:

  • Continuous Integration - Build Status - "build passing" indicates that the project's tests all pass as expected. If you see that the build for a project is "broken" it means the software does not work as advertised! This is a clear sign that you should not be using it (until it gets fixed!) ... check the repo's issues to see if it's a known problem, if not, report it!
    We use Travis CI for our CI. We wrote a little how-to/tutorial to help you (and your team) get started:

  • Test/Code Coverage - Code Coverage - coverage is the measure of how much of the code in a project is tested. Anything below 100% coverage means the module/library has potential bugs which are unknown to the authors/users. We avoid using modules with less than 100% coverage and encourage others to question why the authors did not put in the time to test their code... ALL our code is tested. we cannot guarantee every line is "bug-free", (and always welcome people reporting any issues!) however we are meticulous about testing our work and always add regression/edge test cases where bugs are discovered!

  • CodeClimate - Code Climate - is the code quality score for a project measured on a number of factors including Complexity/Simplicity, Readability, Maintainability, Repetition and Line-count-per-file . The maximum score is 4.0 and we obviously strive to achieve this level in all our work.

  • JavaScript the goodparts (code style/linting) - JavaScript Style Guide: Good Parts ... "Third Party" Code analysis services like CodeClimate (above) are really useful to have an "objective" (impartial) measure for the complexity/maintainability of your codebase, however you may want to take code-style/readability to the next level by using a specific style across all your projects ... Having harmony in your codebase is really useful/practical because it reduces the "thinking time". People working on the project need in order to understand (and thus maintain/extend) existing code. There are a few JavaScript "style guides" which help you & your team write consistent JS. We like goodparts because of these reasons, however we encourage you to make up your own mind as to which style to use (preferably based on sound reasoning not fashion...)

  • Dependencies - Dependency Status - knowing your module/project has (and works with) the latest versions of all its dependencies is a good way to signal that any bug-fixes/performance improvements/security patches etc in the component modules/libraries are considered in by the authors. We use to track our dependencies. david-dm is lovingly maintained by @alanshaw of TableFlip (a fellow dwyler!) and is a great resource for the node.js community!

  • devDependencies - devDependencies Status - your devDependencies are the modules used in testing/building your project. These do not need to be the latest versions because you will typically not install your devDependencies on your production server (so there aren't security vulnerabilities in production of having out-of-date devDependencies...) however, we encourage use of latest devDependencies because it means better stability in the build (fewer bugs in our tools!) and it makes it easier for new people joining the project because when they npm install they know everything is the latest version.

  • NPM Module Version - NPM Version this is a simple convenience to signal to fellow developers which version is the latest for your module. (saves them having to look at the package.json) If you want to include one in your readme, go to: and type in your npm package name.

  • NPM Module Download Stats - NPM Download Stats - while this can be seen as a "vanity metric" it can also be useful to know if your project is actually being used by people in the community to know if you need keep supporting it.


Build Passing Build Status

GitHub Actions/Workflows

If you are using GitHub Actions/Workflows to run your Continuous Integration (CI), then you can include a badge in your project's

Regular badge template:

![example workflow](<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)


![GitHub CI](

GitHub CI

Custom badge via image


![GitHub Workflow Status](

GitHub Workflow Status


You'll need to setup your project on Travis-CI and write unit tests (preferably TDD!) for this to work ... if you're stuck ask us how!

[![Build Status]({ORG-or-USERNAME}/{REPO-NAME}.png?branch=master)]({ORG-or-USERNAME}/{REPO-NAME})


Setup your repository by adding it on code climate then copy the badge markdown from them!

For more detailed instructions see:


The new kid on the block for Test Coverage is "CodeCov":
We love their features especially the fact that they check coverage for pull requests! see:

To setup codecov simply add the following lines to your .travis.yml file:

  - pip install --user codecov
  - codecov --file coverage/ --disable search

And remember to output a coverage report in your tests using istanbul, by adding it to your test script in your package.json so that travis can send the coverage report to codecov e.g:

"scripts": {
  "test": "./node_modules/.bin/istanbul cover ./node_modules/tape/bin/tape ./test/*.js"

If you are new to test coverage using istanbul check out: learn-istanbul

Working example: hits/.travis.yml

Note: you can still use CodeClimate for Coverage if you prefer,
we're excited that there is more choice in the JS testing space!

goodparts JavaScript Code Style JavaScript Style Guide: Good Parts

Once you have installed goodparts and used it to lint your code, see: you can include a badge in your repo to inform others of your choice of code style.

[![JavaScript Style Guide: Good Parts](]( "JavaScript The Good Parts")


Why? start with why

## Why? [![start with why](](

Node.js Version your Project/Module Supports: NPM version

[![Node version]([NPM-MODULE-NAME].svg?style=flat)](

NPM Download Statistics

To show download stats for your NPM package, use e.g:

NPM Download Stats

If you want the image to be clickable use the following Markdown:


Contributing contributions welcome

If you want to encourage people to contribute to your project, by reminding them that you welcome their input use this badge!

## Contributing [![contributions welcome](](

Gitter (Chat for Developers!)

Join the chat at

[![Join the chat at{ORG-or-USERNAME}/{REPO-NAME}](](

dwyl chat button:

If you are working on a project in the dwyl organisation and want to include the button to let people join our public chat channel, copy paste this markdown snippet into the of the project you are working on:

[![Join the chat at](](

(GitHub Repo) Hit Counter HitCount

Ever wanted to know how many people have viewed your GitHub Repo?
We did ... So we wrote a tiny script that counts views! :open_mouth:

Visit: to get your "Hit Count" badge.





Yes, we know that for some people, "hits" = "How Idiots Track Success" ... but, in the absence of better analytics, page views are a good metric to be aware of! :chart_with_upwards_trend:

Snyk Proactive Security Vulnerability Detection


Thank You!

Help spread the Code Quality Love! :heart:
Please :star: this repo and share it with others by re-tweeting:



If you need to adapt any of the images or create your own:

Extra High-resolution

We needed High-resolution versions of the coding badges for a presentation about testing so we made PNGs from the SVGs ...

These are in the folders in this repo in case they are useful to someone else.

1Other repositories that do not have these badges are not necessarily "worse" or have "low standards", they simply are not making them explicit .

Open Source Agenda is not affiliated with "Repo Badges" Project. README Source: dwyl/repo-badges
Open Issues
Last Commit
1 year ago

Open Source Agenda Badge

Open Source Agenda Rating