The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bbo-bbo 0.5.2
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 | |
|---|---|---|---|---|
| bbo_bbo-0.5.2.tar.gz | 44.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bbo_bbo-0.5.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 92.6 kB
Release files / bbo_bbo-0.5.2.tar.gz
| Download URL | bbo_bbo-0.5.2.tar.gz |
|---|---|
| Size | 44.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecc88839c15002cff25229f288a60dc806fd725ee02a717ca183a7ab11d5dbea
|
|
BLAKE2b-256 checksum How to use checksums |
e991d418e463ca87bce361a6353a5ee93260ca25e5559c77e529a2556ba4892f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.2
|
Release files / bbo_bbo-0.5.2-py2.py3-none-any.whl
| Download URL | bbo_bbo-0.5.2-py2.py3-none-any.whl |
|---|---|
| Size | 48.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
9c660b161c8a3ec572e1354a62f752b6a0fc94180525da3aa9255bc31dfdaccb
|
|
BLAKE2b-256 checksum How to use checksums |
934dab0585e2b5b9a16d16d485d657ec6d389ed78dd5f179a8c888d47c38b639
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.2
|
Security for bbo-bbo 0.5.2
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.
