1 maintainer
Metadata
1 maintainer
Release files for bamboxo2go-devlib 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 | |
|---|---|---|---|---|
| bamboxo2go-devlib-0.1.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bamboxo2go_devlib-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / bamboxo2go-devlib-0.1.0.tar.gz
| Download URL | bamboxo2go-devlib-0.1.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0178f470859f2b54d0317ecfb208363597ad29a247e6f421a1c8642974da97c
|
|
BLAKE2b-256 checksum How to use checksums |
879bb0e117297a9ad1f6a15c59d1b6b5d5f3d7b6d9f7fe8f20b27291dfd0adb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Release files / bamboxo2go_devlib-0.1.0-py3-none-any.whl
| Download URL | bamboxo2go_devlib-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0196eb151291a2da9616432f958dd19e0509e39e06e64a76c568844351b14df5
|
|
BLAKE2b-256 checksum How to use checksums |
29aa84e0571518bfba5d5f8c050d37b96790ff27e2bd618e95f9dfd26051d21d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Security for bamboxo2go-devlib 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.
