Release files for bdrocfl 0.6
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 | |
|---|---|---|---|---|
| bdrocfl-0.6.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bdrocfl-0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.7 kB
Release files / bdrocfl-0.6.tar.gz
| Download URL | bdrocfl-0.6.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c59e518ea3f9154606d7892aec4449d90c7196557813ab8cfbebe2222a632cf
|
|
BLAKE2b-256 checksum How to use checksums |
d9e1768a64792ce75afd79b419285dca498eacb4bd37a249fff35219d8ce290e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.21.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.3
|
Release files / bdrocfl-0.6-py3-none-any.whl
| Download URL | bdrocfl-0.6-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa98e19162df265477a9ea4d6c157a7113d48f7aded77253d6e28b84f360585d
|
|
BLAKE2b-256 checksum How to use checksums |
eb77510fa4128f5a8f0f6c8a340db14b1dcf5e01805abc4024aeb93e2edb6056
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.21.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.3
|
Security for bdrocfl 0.6
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.
