The author of this package has not provided a project description
Metadata
Release files for bits-retreat 0.0.23
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 | |
|---|---|---|---|---|
| bits_retreat-0.0.23.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bits_retreat-0.0.23-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.5 kB
Release files / bits_retreat-0.0.23.tar.gz
| Download URL | bits_retreat-0.0.23.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac5819feaf1c44191f29062cf15825e24467004dc40d5050cc295611272325d4
|
|
BLAKE2b-256 checksum How to use checksums |
928c4957199461822edd707af7c6108971e8ff5cc18feb4469e66759b374b9ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / bits_retreat-0.0.23-py3-none-any.whl
| Download URL | bits_retreat-0.0.23-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d1ad261e8737250c5b6ded13de6ed3d5ea1aaabeaa69083ea18830d25c89078
|
|
BLAKE2b-256 checksum How to use checksums |
7874fbf36d4bbf390bb9bcba72987ccc46dd57529720fbba9a07ba481207137d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for bits-retreat 0.0.23
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.