Pixel-perfect Retina-ready Fast Consistent Hackable No tracking
|Azure DevOps coverage:|
|Azure DevOps coverage (branch):|
|Codacy branch coverage:|
|Code Climate coverage:|
|Coveralls github branch:|
|Coveralls bitbucket branch:|
|nycrc config on GitHub:|
|Scrutinizer coverage (GitHub/BitBucket):|
|Scrutinizer coverage (GitLab):|
Using dash "-" separator
Using query string parameters
Create badges from your own JSON endpoint.
The following styles are available. Flat is the default. Examples are shown with an optional logo:
Here are a few other parameters you can use: (connecting several with "&" is possible)
|Override the default left-hand-side text (URL-Encoding needed for spaces or special characters!)|
|Insert one of the named logos from (bitcoin, dependabot, discord, gitlab, npm, paypal, serverfault, stackexchange, superuser, telegram, travis) or simple-icons. Simple-icons are referenced using names as they appear on the simple-icons site. If the name includes spaces, replace them with dashes (e.g: |
|Insert custom logo image (≥ 14px high). There is a limit on the total size of request headers we can accept (8192 bytes). From a practical perspective, this means the base64-encoded image text is limited to somewhere slightly under 8192 bytes depending on the rest of the request header.|
|Set the color of the logo (hex, rgb, rgba, hsl, hsla and css named colors supported). Supported for named logos but not for custom logos.|
|Set the horizontal space to give to the logo|
|Specify what clicking on the left/right of a badge should do (esp. for social badge style)|
|Set background of the left part (hex, rgb, rgba, hsl, hsla and css named colors supported). The legacy name "colorA" is also supported.|
|Set background of the right part (hex, rgb, rgba, hsl, hsla and css named colors supported). The legacy name "colorB" is also supported.|
|Set the HTTP cache lifetime (rules are applied to infer a default value on a per-badge basis, any values specified below the default will be ignored). The legacy name "maxAge" is also supported.|
.json. The default is
.svg, which can be omitted from the URL.
While we highly recommend using SVG, we also support
.png for use cases where SVG will not work. These requests should be made to our raster server
https://raster.shields.io. For example, the raster equivalent of
https://raster.shields.io/v/npm/express. For backward compatibility, the badge server will redirect
.png badges to the raster server.
Have an idea for an awesome new badge?
Tell us about it and we might bring it to you!