anybadge
Python project for generating badges for your projects
Supports: Python 3.7-3.15 (2.7-3.6 support has been dropped)
Overview
anybadge can be used to add badge generation to your Python projects,
and also provides a command line interface.
This utility can be used to generate .svg badge images, using configurable
thresholds for coloring the badges based on the badge value. Many badge
generation tools just provide the ability to specify the color of badge.
anybadge allows you to specify the label, badge value, and color, but
it also allows you to specify a set of thresholds that can be used to
select a color based on the badge value.
anybadge may be useful for companies developing internally, or any time
making calls to external badge services is not possible, or undesirable.
In this situation using anybadge will be easier than running your own
internal badge service.
The package can be imported into your python code, or run direct from the command line.
Demo
You can find a repl.it demo here. This will allow you to see what the package can do and play with it to test outputs.
Basic usage
Command line
As an example, if you want to produce a pylint badge, you may run anybadge
from the command line like this:
anybadge -l pylint -v 2.22 -f pylint.svg 2=red 4=orange 8=yellow 10=green
This would result in a badge like this:
In this example the label is set to "pylint", the value "2.22", and an
output file called "pylint.svg". The thresholds are provided in pairs
of <value>=color Values can be integer or floats for ranges, and
string values are also supported. See
Thresholds below for details of how the badge value is
compared against thresholds.
Python
Here is the same example implemented in Python code:
import anybadge
# Define thresholds: <2=red, <4=orange <8=yellow <10=green
thresholds = {2: 'red',
4: 'orange',
6: 'yellow',
10: 'green'}
badge = anybadge.Badge('pylint', 2.22, thresholds=thresholds)
badge.write_badge('pylint.svg')
Installation
anybadge is available in PyPi at https://pypi.org/project/anybadge
Release notes are published on the GitHub releases page.
You can install the latest release of anybadge using pip:
pip install anybadge
This will install the Python package, and also make anybadge available
as a command line utility.
Support for :emoji: shortcodes (see
Emojis below) is an optional extra since it requires the
emoji package. Install it with:
pip install anybadge[emoji]
Without this extra, :shortcode: text is rendered exactly as it was passed.
Getting help
To get help from the command line utility, just run:
anybadge --help
Command line usage
Output
Running the utility with the --file option will result in the .svg image being
written to file. Without the --file option the .svg file content will be
written to stdout, so can be redirected to a file.
Thresholds
Thresholds are provided as pairs of <threshold>=<color>. Each threshold
defines the upper bound of a range. The badge value is compared against
each threshold in turn, and the color used is that of the first threshold
whose value the badge value is strictly less than. With:
anybadge --label=pylint --value=2.22 --file=pylint.svg 2=red 4=orange 8=yellow 10=green
the thresholds can be read as "less than 2 = red, less than 4 = orange, less than 8 = yellow, less than 10 = green", or shown as a decision flow:
flowchart LR
A([badge value]) --> B{"value < 2?"}
B -- "yes" --> R[red]
B -- "no" --> C{"value < 4?"}
C -- "yes" --> O[orange]
C -- "no" --> D{"value < 8?"}
D -- "yes" --> Y[yellow]
D -- "no" --> E{"value < 10?"}
E -- "yes" --> G[green]
E -- "no" --> G
classDef red fill:#e05d44,color:#fff
classDef orange fill:#fe7d37,color:#fff
classDef yellow fill:#dfb317,color:#000
classDef green fill:#4c1,color:#000
class R red
class O orange
class Y yellow
class G green
Note that the comparison is exclusive (< rather than <=). A value
exactly equal to a threshold is not less than that threshold, so it
falls into the next range up. With the thresholds above:
| Badge value | Badge color | Why |
|---|---|---|
| 1.99 | red | 1.99 is < 2 |
| 2.0 | orange | 2.0 is not < 2, but is < 4 |
| 4.0 | yellow | 4.0 is not < 4, but is < 8 |
| 9.0 | green | 9.0 is not < 8, but is < 10 |
| 10 or greater | green | see "Values above the top threshold" below |
Values above the top threshold default to the color of the largest
threshold. On the command line this behavior is off by default; pass
--use-max to enable it, otherwise the --color value is used.
On the Python API the behavior is on by default; pass
use_max_when_value_exceeds=False to disable it and use default_color
instead.
Lower is better, higher is worse. The exclusive comparison matters most when a badge shows a metric where lower values are good, such as vulnerability or code-quality counts, because a value exactly equal to a threshold has not reached the next level of "goodness". For example, with 0 vulnerabilities being good, and any value of 1 or more being bad:
anybadge --label=vulnerabilities --value=4 --file=vulnerabilities.svg --color=red 1=green
flowchart LR
A([badge value]) --> B{"value < 1?"}
B -- "yes (0)" --> G2[green]
B -- "no (1+)" --> R2[red]
classDef green fill:#4c1,color:#000
classDef red fill:#e05d44,color:#fff
class G2 green
class R2 red
Here the fixed --color=red is used as the default color for values that
do not fall below the single threshold, so a badge value of 0 is green,
and any value of 1 or more is red. The same badge can be created in
Python with:
badge = Badge(
label='vulnerabilities',
value=4,
default_color='red',
thresholds={1: 'green'},
use_max_when_value_exceeds=False,
)
Built-in templates
Some common badge types have been built in to save you from having to specify thresholds, a label, and a value suffix each time. To use one of these built-ins, specify the template name in place of threshold value/color pairs:
anybadge --value=<VALUE> --file=<FILE> <TEMPLATE-NAME>
| Template | Label | Value suffix | Thresholds | Colors produced |
|---|---|---|---|---|
| pylint | pylint |
(none) | 2=red 4=orange 8=yellow 10=green | less than 2 = red, less than 4 = orange, less than 8 = yellow, 10 and above = green |
| coverage | coverage |
% |
50=red 60=orange 80=yellow 100=green | less than 50 = red, less than 60 = orange, less than 80 = yellow, 100 and above = green |
For example:
anybadge --value=2.22 --file=pylint.svg pylint
Any badge can also be customized with a different style using
--style=gitlab-scoped, or with a custom SVG template file using
--template <path>.
Colors
Anybadge comes with some pre-defined colors, which can be referred to by name. It also
supports the use of custom colors by using the hex representation of the color. Both color
types can be used in the default_color, text_color and thresholds attributes. Color names are
taken from the Mozilla color keywords list.
Here is a Python example showing use of a named color and a custom color.
import anybadge
badge = anybadge.Badge(label='custom color', value='teal', default_color='teal', num_padding_chars=1)
badge = anybadge.Badge(label='custom color', value='teal', default_color='#008080', num_padding_chars=1)
Available named colors are:
| Color Name | Hex | Example |
|---|---|---|
| aliceblue | #F0F8FF | |
| antiquewhite | #FAEBD7 | |
| aqua | #00FFFF | |
| aquamarine | #7FFFD4 | |
| azure | #F0FFFF | |
| beige | #F5F5DC | |
| bisque | #FFE4C4 | |
| black | #000000 | |
| blanchedalmond | #FFEBCD | |
| blue | #0000FF | |
| blueviolet | #8A2BE2 | |
| bright_red | #FF0000 | |
| bright_yellow | #FFFF00 | |
| brown | #A52A2A | |
| burlywood | #DEB887 | |
| cadetblue | #5F9EA0 | |
| chartreuse | #7FFF00 | |
| chocolate | #D2691E | |
| coral | #FF7F50 | |
| cornflowerblue | #6495ED | |
| cornsilk | #FFF8DC | |
| crimson | #DC143C | |
| darkblue | #00008B | |
| darkcyan | #008B8B | |
| darkgoldenrod | #B8860B | |
| darkgray | #A9A9A9 | |
| darkgreen | #006400 | |
| darkkhaki | #BDB76B | |
| darkmagenta | #8B008B | |
| darkolivegreen | #556B2F | |
| darkorange | #FF8C00 | |
| darkorchid | #9932CC | |
| darkred | #8B0000 | |
| darksalmon | #E9967A | |
| darkseagreen | #8FBC8F | |
| darkslateblue | #483D8B | |
| darkslategray | #2F4F4F | |
| darkturquoise | #00CED1 | |
| darkviolet | #9400D3 | |
| deeppink | #FF1493 | |
| deepskyblue | #00BFFF | |
| dimgray | #696969 | |
| dodgerblue | #1E90FF | |
| firebrick | #B22222 | |
| floralwhite | #FFFAF0 | |
| forestgreen | #228B22 | |
| fuchsia | #FF00FF | |
| gainsboro | #DCDCDC | |
| ghostwhite | #F8F8FF | |
| gold | #FFD700 | |
| goldenrod | #DAA520 | |
| gray | #808080 | |
| green | #4C1 | |
| greenyellow | #ADFF2F | |
| green_2 | #008000 | |
| honeydew | #F0FFF0 | |
| hotpink | #FF69B4 | |
| indianred | #CD5C5C | |
| indigo | #4B0082 | |
| ivory | #FFFFF0 | |
| khaki | #F0E68C | |
| lavender | #E6E6FA | |
| lavenderblush | #FFF0F5 | |
| lawngreen | #7CFC00 | |
| lemonchiffon | #FFFACD | |
| lightblue | #ADD8E6 | |
| lightcoral | #F08080 | |
| lightcyan | #E0FFFF | |
| lightgoldenrodyellow | #FAFAD2 | |
| lightgray | #D3D3D3 | |
| lightgreen | #90EE90 | |
| lightpink | #FFB6C1 | |
| lightsalmon | #FFA07A | |
| lightseagreen | #20B2AA | |
| lightskyblue | #87CEFA | |
| lightslategray | #778899 | |
| lightsteelblue | #B0C4DE | |
| lightyellow | #FFFFE0 | |
| light_grey | #9F9F9F | |
| lime | #00FF00 | |
| limegreen | #32CD32 | |
| linen | #FAF0E6 | |
| maroon | #800000 | |
| mediumaquamarine | #66CDAA | |
| mediumblue | #0000CD | |
| mediumorchid | #BA55D3 | |
| mediumpurple | #9370DB | |
| mediumseagreen | #3CB371 | |
| mediumslateblue | #7B68EE | |
| mediumspringgreen | #00FA9A | |
| mediumturquoise | #48D1CC | |
| mediumvioletred | #C71585 | |
| midnightblue | #191970 | |
| mintcream | #F5FFFA | |
| mistyrose | #FFE4E1 | |
| moccasin | #FFE4B5 | |
| navajowhite | #FFDEAD | |
| navy | #000080 | |
| oldlace | #FDF5E6 | |
| olive | #808000 | |
| olivedrab | #6B8E23 | |
| orange | #FE7D37 | |
| orangered | #FF4500 | |
| orange_2 | #FFA500 | |
| orchid | #DA70D6 | |
| palegoldenrod | #EEE8AA | |
| palegreen | #98FB98 | |
| paleturquoise | #AFEEEE | |
| palevioletred | #DB7093 | |
| papayawhip | #FFEFD5 | |
| peachpuff | #FFDAB9 | |
| peru | #CD853F | |
| pink | #FFC0CB | |
| plum | #DDA0DD | |
| powderblue | #B0E0E6 | |
| purple | #800080 | |
| rebeccapurple | #663399 | |
| red | #E05D44 | |
| rosybrown | #BC8F8F | |
| royalblue | #4169E1 | |
| saddlebrown | #8B4513 | |
| salmon | #FA8072 | |
| sandybrown | #F4A460 | |
| seagreen | #2E8B57 | |
| seashell | #FFF5EE | |
| sienna | #A0522D | |
| silver | #C0C0C0 | |
| skyblue | #87CEEB | |
| slateblue | #6A5ACD | |
| slategray | #708090 | |
| snow | #FFFAFA | |
| springgreen | #00FF7F | |
| steelblue | #4682B4 | |
| tan | #D2B48C | |
| teal | #008080 | |
| thistle | #D8BFD8 | |
| tomato | #FF6347 | |
| turquoise | #40E0D0 | |
| violet | #EE82EE | |
| wheat | #F5DEB3 | |
| white | #FFFFFF | |
| whitesmoke | #F5F5F5 | |
| yellow | #DFB317 | |
| yellowgreen | #9ACD32 | |
| yellow_green | #A4A61D |
Emojis
It is possible to use emoji characters in badge labels and values. Here are some examples:
These files were created by using the actual emoji character in the label/value text. For example:
badge = anybadge.Badge(label="Pipeline status", value="😄")
If you install the emoji extra (pip install anybadge[emoji]), you can
instead write :shortcode: text in labels and values, and it will be
automatically converted into emoji characters before the badge is rendered.
This is useful in editors and consoles where typing emoji characters is
difficult. Both Unicode CLDR shortcodes and GitHub-style aliases are
supported:
badge = anybadge.Badge(label="Pipeline status", value=":smile:")
# :smile: is a GitHub-style alias for 😄
badge = anybadge.Badge(label="Pipeline status", value=":grinning_face:")
# :grinning_face: is a Unicode CLDR shortcode for 😀
See the emoji package documentation for the full list of
supported shortcodes. Without the emoji package, :shortcode: text is rendered
as-is.
Here are the same badges generated with an actual emoji character, with
shortcodes (using the emoji package), and with shortcodes where the emoji
package is not installed. Note that a badge created with a shortcode renders
exactly the same as one created with the emoji character itself:
| Badge | Code |
|---|---|
anybadge.Badge(label="Pipeline status", value="😄") — actual emoji character |
|
anybadge.Badge(label="Pipeline status", value=":smile:") — shortcode (requires emoji package) |
|
anybadge.Badge(label="Pipeline status", value=":smile:") — without emoji package: rendered as-is |
|
anybadge.Badge(label=":rocket: Deploy", value=":100:") — shortcodes in label and value |
Emoji conversion happens before badge dimensions are calculated, so emoji shortcodes take up exactly the same space as the emoji characters they produce. Note that the original text is used when matching values against thresholds, so thresholds should be defined using the text you pass as the value.
There are some caveats worth mentioning:
- The "look" of the emoji is determined by the client (Emoji characters are placed as-is into the SVG file, and are rendered client-side)
- Rendering may fail in some viewers and developer IDEs (for example, PyCharm does not render emojis in the svg viewer)
- Emoji fallback fonts render emoji at a visually smaller size than Latin text at the same font size, so
anybadge wraps emoji characters in
<tspan>elements that render them slightly larger, at 3pt above the surrounding font size (e.g. 14 when the font size is 11). You can change this with theemoji_font_sizeargument, or--emoji-font-sizeon the command line. To render emoji at the surrounding font size without the tspan wrapper, passemoji_font_sizeequal tofont_size. - Emojis can have different widths, so the layout may be affected. You can use
num_label_padding_charsandnum_value_padding_charsto fix (see below)
Here are some examples to show how to use padding to fix layout:
| Badge | Code |
|---|---|
anybadge.Badge("Pipeline status", "😄") |
|
anybadge.Badge("Pipeline status", "😄", num_value_padding_chars=1) |
Logos
Badges can include a logo, positioned next to the label or value. A logo can
be specified as a Simple Icons slug, a local image file path, an http(s)
URL, or a data: URI. In all cases the image is embedded into the badge
as a base64 data: URI, so the generated SVG remains fully
self-contained and never loads anything at view time.
Common project logos are bundled with the package (rendered in white to match the badge text color), and can be used offline:
docker git github gitlab javascript jenkins kubernetes
linux nodejs python typescript
Bundled logos are sourced from Simple Icons and released under a CC0 1.0 public domain dedication. All logos remain subject to their respective brand owners' trademarks and usage guidelines.
| Badge | Code |
|---|---|
anybadge.Badge("Stars", "23,414", logo="github") |
|
anybadge.Badge("Stars", "23,414", logo="github", logo_position="right") |
|
anybadge.Badge("Python", "3.13", logo="python") |
|
anybadge.Badge("Docker", "passing", logo="docker") |
Logos that are not bundled can be provided as:
badge = anybadge.Badge(label="Stars", value="23,414", logo="https://cdn.simpleicons.org/github/red")
badge = anybadge.Badge(label="Stars", value="23,414", logo="logos/mysprite.svg")
badge = anybadge.Badge(label="Stars", value="23,414", logo="mysprite",
logo_dirs=["logos"])
When a Simple Icons slug is given, logo_color chooses the icon color for
CDN downloads (e.g. logo_color="#fff"); bundled, vendored and local-file
logos use the colors stored in the image file.
Using logos in network-gated environments
If badges are generated on a CI runner or server that is gated from the network, logos can be vendored as files wherever network access is available, and then used from disk:
# Where there is network access, download logos into a directory
# (e.g. commit this directory, or pass it between CI jobs):
anybadge fetch-logos python github docker --dir=logos
# Where there is no network access, generate badges using vendored logos:
anybadge --label=stars --value=23414 --logo=github --logos-dir=logos --file=stars.svg
The same resolution applies in Python, using the logo_dirs argument.
The parameters are also accepted by anybadge-server, as logo,
logo_color and logo_position query parameters:
http://localhost:8000/?label=Stars&value=23414&logo=github&logo_position=right
The server additionally takes a --logos-dir argument (repeatable),
which is used to resolve logo names, so a server on a network-gated
host can generate badges containing vendored logos without network
access.
Value or label only
It is possible to create badges with only a label or only a value. This can be done by passing an empty string to the appropriate field. Note that either a label or value must be provided.
| Badge | Code |
|---|---|
anybadge.Badge(label="Label only") |
|
anybadge.Badge(value="Value only") |
Semantic version support
Anybadge supports semantic versions for value and threshold keys. This supports color-coded badges based on version numbering. Here are some examples:
badge = Badge(
label='Version',
value='3.0.0',
thresholds={'3.0.0': 'red', '3.2.0': 'orange', '999.0.0': 'green'},
semver=True
)
In the above example the thresholds equate to the following:
- If value is < 3.0.0 then badge will be red.
- If value is < 3.2.0 then badge will be orange.
- If value is < 999.0.0 then badge will be green.
Each threshold entry is used to define the upper bounds of the threshold. If you don't know the
upper bound for your version number threshold you will need to provide an extreme upper bound -
in this example it is 999.0.0.
Escaping
Badges are generated as .svg files, which utilize an XML-based markup language. Consequently, any HTML characters present in badge labels or values must be escaped to ensure proper representation. If you need to disable escaping, the following options are available:
- Python API
escape_label=Falseescape_value=False
- CLI
--no-escape-label--no-escape-value
Examples
Pylint using template
anybadge --value=2.22 --file=pylint.svg pylint
Pylint using arguments
anybadge -l pylint -v 2.22 -f pylint.svg 2=red 4=orange 8=yellow 10=green
Coverage using template
anybadge --value=65 --file=coverage.svg coverage
Pipeline, using labeled colors
anybadge --label=pipeline --value=passing --file=pipeline.svg passing=green failing=red
Badge with fixed color
anybadge --label=awesomeness --value="110%" --file=awesomeness.svg --color='#97CA00'
GitLab Scoped style badge
anybadge --style=gitlab-scoped --label=Project --value=Archimedes --file=gitlab_scoped.svg --color='#c1115d'
Thresholds based on semantic versions
anybadge --label=Version --value=2.4.5 --file=version.svg 1.0.0=red 2.4.6=orange 2.9.1=yellow 999.0.0=green
Importing in your own app
from anybadge import Badge
test1 = Badge(
label,
value,
font_name='DejaVu Sans,Verdana,Geneva,sans-serif',
font_size=11,
num_padding_chars=0.5,
template='<?xml version="1.0" encoding="UTF-8"?>\n<svg xmlns="http://www.w3.org/2000/svg" width="{{ badge width }}" height="20">\n <linearGradient id="b" x2="0" y2="100%">\n <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>\n <stop offset="1" stop-opacity=".1"/>\n </linearGradient>\n <mask id="a">\n <rect width="{{ badge width }}" height="20" rx="3" fill="#fff"/>\n </mask>\n <g mask="url(#a)">\n <path fill="#555" d="M0 0h{{ color split x }}v20H0z"/>\n <path fill="{{ color }}" d="M{{ color split x }} 0h{{ value width }}v20H{{ color split x }}z"/>\n <path fill="url(#b)" d="M0 0h{{ badge width }}v20H0z"/>\n </g>\n <g fill="{{ label text color }}" text-anchor="middle" font-family="{{ font name }}" font-size="{{ font size }}">\n <text x="{{ label anchor shadow }}" y="15" fill="#010101" fill-opacity=".3">{{ label }}</text>\n <text x="{{ label anchor }}" y="14">{{ label }}</text>\n </g>\n <g fill="{{ value text color }}" text-anchor="middle" font-family="{{ font name }}" font-size="{{ font size }}">\n <text x="{{ value anchor shadow }}" y="15" fill="#010101" fill-opacity=".3">{{ value }}</text>\n <text x="{{ value anchor }}" y="14">{{ value }}</text>\n </g>\n</svg>',
value_prefix='',
value_suffix='',
thresholds=None,
default_color='#4c1',
use_max_when_value_exceeds=True,
value_format=None,
text_color='#fff'
)
test1.write_badge('test1.svg')
Command-line options
The command line options can be viewed using anybadge --help.
Examples
Here are some usage specific command line examples that may save time on defining thresholds.
Pylint::
anybadge.py --value=2.22 --file=pylint.svg pylint
anybadge.py --label=pylint --value=2.22 --file=pylint.svg 2=red 4=orange 8=yellow 10=green
Coverage::
anybadge.py --value=65 --file=coverage.svg coverage
anybadge.py --label=coverage --value=65 --suffix='%%' --file=coverage.svg 50=red 60=orange 80=yellow 100=green
CI Pipeline::
anybadge.py --label=pipeline --value=passing --file=pipeline.svg passing=green failing=red
Python usage
For Python API details you can use the inbuilt documentation:
from anybadge import badge
help(badge)
Metadata
Release files for anybadge 1.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| anybadge-1.18.0.tar.gz | 186.3 kB | With provenance | Details for anybadge-1.18.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anybadge-1.18.0-py3-none-any.whl | Python 3 | none | any | Details for anybadge-1.18.0-py3-none-any.whl |
Total release size: 243.0 kB
Release files / anybadge-1.18.0.tar.gz
| Download URL | anybadge-1.18.0.tar.gz |
|---|---|
| Size | 186.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f275a1aa14a8d04d1043b420550504eb72d44d222fea78e2a6a0347f8a2e6e3
|
|
BLAKE2b-256 checksum How to use checksums |
293c6130b92cc11cd962628a095ee5adb7c8fa4dd5091539dcb314f019376946
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logRelease files / anybadge-1.18.0-py3-none-any.whl
| Download URL | anybadge-1.18.0-py3-none-any.whl |
|---|---|
| Size | 56.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7924f3dbf355f412aa4bff4e90bf4079787299144408cc71d094c9ab96ab4a26
|
|
BLAKE2b-256 checksum How to use checksums |
666bad135215631611a7758760d298d14e2fa93b2f4216f65e0cba15bd75b216
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logSecurity for anybadge 1.18.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for anybadge-1.18.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.