Cppcheck Python distribution
This project packages the cppcheck utility as a Python package. It allows you to install cppcheck directly from PyPI:
python -m pip install cppcheck-py
The tools provided are:
cppcheck: performs static analysis of C/C++ source code cppcheck-htmlreport: generates an html report of a XML file produced by cppcheck
This projects intends to release a new PyPI package for each major and minor release of cppcheck.
Use with pipx
You can use pipx to run cppcheck, as well. For example, pipx run cppcheck <args> will run cppcheck without any previous install required on any machine with pipx (including all default GitHub Actions / Azure runners, avoiding requiring a pre-install step or even actions/setup-python).
Building new releases
The cppcheck-wheel repository provides the logic to build and publish binary wheels of the cppcheck utility.
In order to add a new release, the following steps are necessary:
- Edit the version file
- In the form
cppcheck_version.wheel_version, e.g.2.21.0.1
- In the form
- Tag the commit with this version to trigger the GitHub Actions release workflow
- e.g.
git tag v2.21.0.1 && git push origin v2.21.0.1
- e.g.
Alternatively, the workflow can be triggered manually:
On manual triggers, the following input variables are available:
cppcheck_version: Override the Cppcheck version (default:"")wheel_version: Override the wheel packaging version (default"0")skip_emulation: Set which emulation builds to skip, e.g."qemu"(default:"")deploy_to_testpypi: Whether to deploy to TestPyPI instead of PyPI (default:false)
The repository with the precommit hook is automatically updated using a scheduled Github Actions workflow.
Acknowledgements
This repository extends the great work of several other projects:
cppcheckitself is provided by the Cppcheck project under the GPL-3.0 License.- The repository is inspired by clang-format-wheel and clang-tidy-wheel which are in turn based on scikit-build-core which greatly reduces the amount of low level code necessary to package
cppcheck. - The
scikit-buildpackaging examples of CMake and Ninja were very helpful in packagingcppcheck. - The CI build process is controlled by cibuildwheel which makes building wheels across a number of platforms a pleasant experience (!)
We are grateful for the generous provisioning with CI resources that GitHub currently offers to Open Source projects.
Troubleshooting
To see which cppcheck binary the package is using
you can set CPPCHECK_WHEEL_VERBOSE to 1 in your environment.
1 maintainer
Metadata
1 maintainer
Release files for cppcheck-py 2.16.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 | |
|---|---|---|---|
| cppcheck_py-2.16.0.tar.gz | 12.1 kB | Details |
Built distributions (wheels)
Total release size: 114.1 MB
Release files / cppcheck_py-2.16.0.tar.gz
| Download URL | cppcheck_py-2.16.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15e7b4ddfc5c6888c210bda63167ea1e8ddd99b3ef4864ebefdeabf8c50a80a7
|
|
BLAKE2b-256 checksum How to use checksums |
93ab1d4d32c9dc9cfa807a7d62956c160a9611322f61870470789bbd6f7df4ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-win_arm64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-win_arm64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
cea0d969734f4a014974fd7cfe4f9e3ac08fa0aec77a45b439ba65003fa42616
|
|
BLAKE2b-256 checksum How to use checksums |
24c243cd2507332ea8a326a931913973c731a0f27e995265cb80433319724252
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-win_amd64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-win_amd64.whl |
|---|---|
| Size | 6.4 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
917e60564d43cc3d222f3552c38eee87c154a90b608bf7769991b5f40216469b
|
|
BLAKE2b-256 checksum How to use checksums |
40d29536f4270698f3dff90ea0d0f66e57526c137a06f95ab718c13df380769d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_x86_64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
1730cd3009652315d991d496f4c3fd421483fd8c2c18ce41d9e306d338fc04ba
|
|
BLAKE2b-256 checksum How to use checksums |
326fc11652f8a6c5b49848ec6945fb9713925b90c98863b2640a5552bfc66fca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_s390x.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_s390x.whl |
|---|---|
| Size | 8.1 MB |
| Tags | Linux musl 1.2+ IBM System/390x Python 3 |
|
SHA-256 checksum How to use checksums |
525579117699b83295858999d16b99a05625956a56e3c49606ac232e01bb627e
|
|
BLAKE2b-256 checksum How to use checksums |
d36e59249b52a377a72fc43f7e0a9d518dc4f2b0d05cd780bcf38b0a4b3ff824
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_ppc64le.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_ppc64le.whl |
|---|---|
| Size | 8.2 MB |
| Tags | Linux musl 1.2+ PowerPC 64-le Python 3 |
|
SHA-256 checksum How to use checksums |
f9e013c8f13155000fc3aa126c0a9b1eb0a42e34f10ca14cbd7cbed6303c3739
|
|
BLAKE2b-256 checksum How to use checksums |
3071a51ee17f4b6151d0b1103cc4412d6bfe8d643c28411421daf9764907357e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_i686.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_i686.whl |
|---|---|
| Size | 8.4 MB |
| Tags | Linux musl 1.2+ x86-32 Python 3 |
|
SHA-256 checksum How to use checksums |
87d791623a80f43a4a66393b8607f9455bc9049a497e5d2b123c5a12531985b8
|
|
BLAKE2b-256 checksum How to use checksums |
1332583908fd63aaa548d905e41ab8c47f969b68db57c5ebabee715f7778b71e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_armv7l.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_armv7l.whl |
|---|---|
| Size | 7.4 MB |
| Tags | Linux musl 1.2+ ARMv7l Python 3 |
|
SHA-256 checksum How to use checksums |
8609ed5be52d0c610245d6dc04b96793e3108aef718facdfea1bc8b23cd7fe6f
|
|
BLAKE2b-256 checksum How to use checksums |
d9c644c55f82441e8ba04d248eecc0161d19e2a3e5cce6527371d2c2fa0bf55f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-musllinux_1_2_aarch64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 7.7 MB |
| Tags | Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
c30bd9b0a49d91f852b481276317fc59e3ce1c91588a69f5d27c3b251272a0b0
|
|
BLAKE2b-256 checksum How to use checksums |
545303a8278834323065d6fc6ff5b408775744b2cefc66d4c7d2f082fc5ded18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_35_armv7l.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_35_armv7l.whl |
|---|---|
| Size | 6.4 MB |
| Tags | Linux glibc 2.35+ ARMv7l Python 3 |
|
SHA-256 checksum How to use checksums |
a5a3a0797512b4f060845e8f1a49cb1665b4eba6cc966302caaffab938d88954
|
|
BLAKE2b-256 checksum How to use checksums |
608fdd3bb75c7347d25ca36a632fad89ae4f45731f09dfb1fd83404eed1a28e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_28_i686.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_28_i686.whl |
|---|---|
| Size | 6.9 MB |
| Tags | Linux glibc 2.28+ x86-32 Python 3 |
|
SHA-256 checksum How to use checksums |
040671fa399730aaf4fb41b2fe36fbaaabc8c47ad7f874cf0fe18da2eb7b9429
|
|
BLAKE2b-256 checksum How to use checksums |
d1d65351b649d6e0238383561f91f2a03e684106d3db45a7771c2811579a47da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
9b2f606c8cacefdd178fae172c654dc82f6c426299746c8d9a8758a1c3479153
|
|
BLAKE2b-256 checksum How to use checksums |
1a3180a41374817c5691c32834f9f29a6fd5d52eea70ff0da97f9013d063a874
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_26_s390x.manylinux_2_28_s390x.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_26_s390x.manylinux_2_28_s390x.whl |
|---|---|
| Size | 6.9 MB |
| Tags | Linux glibc 2.26+ IBM System/390x Linux glibc 2.28+ IBM System/390x Python 3 |
|
SHA-256 checksum How to use checksums |
4730a99c9f0c2f2eaf7dbb8746d49f28ff0f06ace1ef33d844fe53b7d64b3fc3
|
|
BLAKE2b-256 checksum How to use checksums |
a3e3c204e3e5da5cc1b858f1ed973058c4aa3bda58be2ca2896eaa019730bedb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_26_ppc64le.manylinux_2_28_ppc64le.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_26_ppc64le.manylinux_2_28_ppc64le.whl |
|---|---|
| Size | 7.0 MB |
| Tags | Linux glibc 2.26+ PowerPC 64-le Linux glibc 2.28+ PowerPC 64-le Python 3 |
|
SHA-256 checksum How to use checksums |
7e54b79e2ae2a91d725af8635acf36be803a489182235940ceca1c2db701ae39
|
|
BLAKE2b-256 checksum How to use checksums |
b86bac50678983c8a14d6c2fe591ccb74d3f67e3d2115d9bcd157a0838ea2ade
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
417e5874d5f39945c8a6a7fcdc5dc1a9d5c32254b01e9e373698873a70720a42
|
|
BLAKE2b-256 checksum How to use checksums |
8b342ef99748037b362bb6710953ee8dcc7b6c7059c5efc0fd6c45b960ec891c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-macosx_11_0_arm64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.4 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2e28ea29b5572b12ab02b47782f1d537a058a2474f28f8cd5b0bf16a6bf13804
|
|
BLAKE2b-256 checksum How to use checksums |
7843b909ee41a482d448c2dd0c5f22ea4f41241307dab236719d7242d05f2ca1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency logRelease files / cppcheck_py-2.16.0-py3-none-macosx_10_9_x86_64.whl
| Download URL | cppcheck_py-2.16.0-py3-none-macosx_10_9_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | Python 3 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
9f2f8e33a11727cd8f4a7e93d20d15d82757fa1dc0efb0844881b4e3bd076a5e
|
|
BLAKE2b-256 checksum How to use checksums |
1a5ee6bdd268592d34ee3ecd0ea19266ab1b4321b6c2faba7468ec0cd2b71908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 12, 2026.
Transparency log
