1 maintainer
Metadata
1 maintainer
Release files for pytest-cocotb-cov 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 | |
|---|---|---|---|---|
| pytest_cocotb_cov-0.1.0.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_cocotb_cov-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.4 kB
Release files / pytest_cocotb_cov-0.1.0.tar.gz
| Download URL | pytest_cocotb_cov-0.1.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fed8da5da4a2ac8d7cd04cafc4fac7255f6f661848da63e6b0e492bf751c4b7
|
|
BLAKE2b-256 checksum How to use checksums |
281175252a1935c7d847dddfd6911ee707a25faea5d8f8fc4b0b9b152b66b3a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / pytest_cocotb_cov-0.1.0-py3-none-any.whl
| Download URL | pytest_cocotb_cov-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9ed694cb659b39edb3c6a140ec9b2ce76bec768c7e2791175d96a1dd3e1faea
|
|
BLAKE2b-256 checksum How to use checksums |
d9a74e17f1ccbabc11c066b8947cbfb6eef1018699a76276f218dfd4d4c9a781
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for pytest-cocotb-cov 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.
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.
