The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aura-s 0.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 | |
|---|---|---|---|---|
| aura_s-0.1.0.tar.gz | 110.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aura_s-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.0 kB
Release files / aura_s-0.1.0.tar.gz
| Download URL | aura_s-0.1.0.tar.gz |
|---|---|
| Size | 110.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36a5e2e4a708aad2446b65c672686a56fcc82103ddedfab0d923211813d9dd61
|
|
BLAKE2b-256 checksum How to use checksums |
19a994eb5219099f289d2052d34ff8d115ac7c04b7d571c80b4e30633a5045e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / aura_s-0.1.0-py3-none-any.whl
| Download URL | aura_s-0.1.0-py3-none-any.whl |
|---|---|
| Size | 100.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4846e1ef3d6809cb52ac56568c5f38e02140d8f9363ae11d29dd8bb9b2649fd9
|
|
BLAKE2b-256 checksum How to use checksums |
b39b8566965764cd70c5d07a81ef8aabe97b5d5fc42386eb7f2997b8d5da5646
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for aura-s 0.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.
