The author of this package has not provided a project description
Metadata
Release files for aengine 1.0.52
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 | |
|---|---|---|---|---|
| AEngine-1.0.52.tar.gz | 33.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| AEngine-1.0.52-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 80.6 kB
Release files / AEngine-1.0.52.tar.gz
| Download URL | AEngine-1.0.52.tar.gz |
|---|---|
| Size | 33.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24a1b5cc9928267f75b4b1d7623fc01d9aaa16c13ea33e476811f3b445e321fd
|
|
BLAKE2b-256 checksum How to use checksums |
6e6606a4ae295e858bd352b2b3a91e7f9818f0f0bfb9187ebd864d4971148a6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.2 Windows/10
|
Release files / AEngine-1.0.52-py3-none-any.whl
| Download URL | AEngine-1.0.52-py3-none-any.whl |
|---|---|
| Size | 47.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09ce542e8dae0b819d04d621ca040caa66d69121d0b2cf27b8882067f06b73a5
|
|
BLAKE2b-256 checksum How to use checksums |
4cdb91f0975f0ba0b118692744788a6174a235d6af7b8dcd0f6a527417fc6b4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.2 Windows/10
|
Security for aengine 1.0.52
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.