Experimental Python Omni Reporter
Release 0.0.1 - 0.0.2 - 2022/02/04
Support for GoLang generated reports. In the same way as CoveragePy, it assumes that all files located in the root with out extension, to be these coverage files.
To know more about these unique reports, please have a look at the document I've written about it here
Release 0.0.0 - 2022/01/24
- 1 file on the root folder
- Env variables: CODACY_PROJECT_TOKEN, CODECOV_TOKEN and COVERALLS_REPO_TOKEN
- More info on how reporting works in the project that started all Omni modules: https://github.com/JEsperancinhaOrg/omni-reporter-maven-plugin
1 maintainer
Metadata
1 maintainer
Release files for omni-coveragereporter 0.0.3
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 |
|---|---|---|---|---|
| omni_coveragereporter-0.0.3.tar.gz | 8.1 kB | Without provenance | Details for omni_coveragereporter-0.0.3.tar.gz |
Release files / omni_coveragereporter-0.0.3.tar.gz
| Download URL | omni_coveragereporter-0.0.3.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d354db74cfdf1af3abeba9d89b56b0c766710e75445313aaa053e75a7ca085b8
|
|
BLAKE2b-256 checksum How to use checksums |
48c7b34314a6fefdbbbf7fdfe8342e0635847163a4d44a0ba9683fd4147f0ba2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.10
|
Security for omni-coveragereporter 0.0.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
