1 maintainer
Metadata
1 maintainer
Release files for AutomateGoFiveLib 1.0.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 | |
|---|---|---|---|---|
| automategofivelib-1.0.2.tar.gz | 28.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| automategofivelib-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.5 kB
Release files / automategofivelib-1.0.2.tar.gz
| Download URL | automategofivelib-1.0.2.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59367fb7c6f26820a0d8592dda2578255ea0e53e0dfb095d8c8d771c1c6551ec
|
|
BLAKE2b-256 checksum How to use checksums |
c846fcf5996c5a3572f612447dff1b2563a3ceee461f74afcfb383c57bfc2305
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / automategofivelib-1.0.2-py3-none-any.whl
| Download URL | automategofivelib-1.0.2-py3-none-any.whl |
|---|---|
| Size | 36.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd70bdb2c8b25bc58a7bf4774c9975fb1d2c1829937a60b2e1874f5a2562a183
|
|
BLAKE2b-256 checksum How to use checksums |
071a15a9c3ac977388851a4b01ce32782937a4abb3c09a4de02a1c87afe98c2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for AutomateGoFiveLib 1.0.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.
