The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ascengine 0.0.3
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 | |
|---|---|---|---|---|
| ascengine-0.0.3.tar.gz | 6.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ascengine-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.2 kB
Release files / ascengine-0.0.3.tar.gz
| Download URL | ascengine-0.0.3.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d48df37d6c6fd09ec928622f22117c4858047712be724c36aaa6b1c59159595
|
|
BLAKE2b-256 checksum How to use checksums |
5cd54433644c081bea8d2bfe6c84deb1a126607d776c2396b4d97faa0aee184c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / ascengine-0.0.3-py3-none-any.whl
| Download URL | ascengine-0.0.3-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99f1792b6e8a053f3708de78eb5c630a3a97ecb0f3c2be7d4030c0e0577799f8
|
|
BLAKE2b-256 checksum How to use checksums |
dfcaa2104505c2c6fcf879ea4966e4e09d3fd69273344f14bb9dec43398ae494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for ascengine 0.0.3
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.
