The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for BA22004UNO 1.0.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 | |
|---|---|---|---|---|
| ba22004uno-1.0.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ba22004uno-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / ba22004uno-1.0.0.tar.gz
| Download URL | ba22004uno-1.0.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87c1a58522a338f949bfae5dbac4c632b5ba9a2c37fd27bc8662cac970b7abe7
|
|
BLAKE2b-256 checksum How to use checksums |
3dabd9db71b2333c5b4ca4d82df1bb66267549313ab69a6cc1fa57ba9dea852a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / ba22004uno-1.0.0-py3-none-any.whl
| Download URL | ba22004uno-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab69c2001d0103035fcab399d7193289b99039b8c0d72d4409f47e0b947263e4
|
|
BLAKE2b-256 checksum How to use checksums |
be9b8fdd4ad1f64d8488b9bd8a923fca7286da75d63e216dbfc5f6d9eea3c009
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for BA22004UNO 1.0.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.
