C++ Code Coverage
A small coverage tooling project for generating coverage reports and a static website view from test outputs.
Installation
pip install cpp-coverage
Quick start
# Generate coverage reports and website data from an instrumented test binary.
coverage-analytics profile --test-binary build/Debug/coverage_example \
--output-directory build/coverage_example_output
# Analyze coverage of lines changed since main.
coverage-analytics diff main --coverage build/coverage_example_output
# Enforce the changed-coverage gate in CI (GitHub Actions).
coverage-analytics diff "$BASE_SHA...HEAD" --coverage build/coverage_example_output \
--format json > diff-coverage.json
coverage-analytics gate diff-coverage.json
Documentation
Getting started
Guides
Reference
License
Copyright (c) 2026 Andrew J. Sender (AndrewJ.Sender@gmail.com)
This project is licensed under the MIT License. See LICENSE for details.
Metadata
Release files for cpp-coverage 0.1.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 |
|---|---|---|---|---|
| cpp_coverage-0.1.0.tar.gz | 36.2 kB | With provenance | Details for cpp_coverage-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cpp_coverage-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cpp_coverage-0.1.0-py3-none-any.whl |
Total release size: 69.7 kB
Release files / cpp_coverage-0.1.0.tar.gz
| Download URL | cpp_coverage-0.1.0.tar.gz |
|---|---|
| Size | 36.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45043827269eec27eaee8ba079375be15d84eadeb2fb9ec68e0e7fa4e4763069
|
|
BLAKE2b-256 checksum How to use checksums |
d43141e2d27277013114ed13745112d33a0b635b4f0a7700ce5e03408181afb9
|
| 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 3, 2026.
Transparency logRelease files / cpp_coverage-0.1.0-py3-none-any.whl
| Download URL | cpp_coverage-0.1.0-py3-none-any.whl |
|---|---|
| Size | 33.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e48eb24d67d1b1deff025d0b87e9120e66d5a404953f6f5a24364a36de9820d9
|
|
BLAKE2b-256 checksum How to use checksums |
4f9f4ff7a579a7bbd19bfac3fb70fc672f7b4beb1d20c9e05b93a4f0f5f3c430
|
| 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 3, 2026.
Transparency logSecurity for cpp-coverage 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cpp_coverage-0.1.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 3, 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.