The author of this package has not provided a project description
Metadata
Release files for agba-engine 5.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 | |
|---|---|---|---|---|
| agba_engine-5.1.0.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agba_engine-5.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / agba_engine-5.1.0.tar.gz
| Download URL | agba_engine-5.1.0.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ce272cb006ba878468c09c18e4a84d98a6ce51c5b50e8c0ef024700fe4a0bd3
|
|
BLAKE2b-256 checksum How to use checksums |
ca51b5bb34c4fe3deaa0431e90e476660844a3a541893d3c50e181351c2615f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Release files / agba_engine-5.1.0-py3-none-any.whl
| Download URL | agba_engine-5.1.0-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ee929ba59b7a42e2485c2ac2494ce63c3b3c77d2ea7c6c63dc77d3145703958
|
|
BLAKE2b-256 checksum How to use checksums |
20d7d03cfb7128362f0df188d0d969db51b1e2d0b2d1dccfd7e7f1ec7ec22f1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Security for agba-engine 5.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.