The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aspirart 0.1.1
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 | |
|---|---|---|---|---|
| aspirart-0.1.1.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aspirart-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 kB
Release files / aspirart-0.1.1.tar.gz
| Download URL | aspirart-0.1.1.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
363fb46493f8f84b07018b6f09a3642465bf92c2fcab166e9576fd3bba303ab1
|
|
BLAKE2b-256 checksum How to use checksums |
c89f3740f4f47982e895b6cfa2abb6b05f19783590a965f2b7f61f78e0af94dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.7
|
Release files / aspirart-0.1.1-py3-none-any.whl
| Download URL | aspirart-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
032b0f18a48d57eda539d6af3fd3d39a796219a1ad48e38f3fcbf19407ac09f0
|
|
BLAKE2b-256 checksum How to use checksums |
7c83585a724ca1f0305d3b10f8b6dba768c4717eab0f739ee8bddd811d558d0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.7
|
Security for aspirart 0.1.1
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.
