The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for b2stats 0.1.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 | |
|---|---|---|---|---|
| b2stats-0.1.3.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| b2stats-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 kB
Release files / b2stats-0.1.3.tar.gz
| Download URL | b2stats-0.1.3.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abcb2ead6d491c878e518e1f34e824629b5df00c28804c2249af337836ee9c03
|
|
BLAKE2b-256 checksum How to use checksums |
9140541b030e661c26d1659632a6620d92a9914d659db55ac47458ee31537654
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / b2stats-0.1.3-py3-none-any.whl
| Download URL | b2stats-0.1.3-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
640d9571231555c7c96e7e80f0d552ed3199ecd596920a373711e14aac5b40a5
|
|
BLAKE2b-256 checksum How to use checksums |
8044675440d923c640aba18177a2bd7e6accc0840a4198ccb20c328fc7dd992e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for b2stats 0.1.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.
