The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aurora-trial 0.0.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 | |
|---|---|---|---|---|
| aurora_trial-0.0.1.tar.gz | 974 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aurora_trial-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 kB
Release files / aurora_trial-0.0.1.tar.gz
| Download URL | aurora_trial-0.0.1.tar.gz |
|---|---|
| Size | 974 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15c40e058e26cc193cd87f36ecfbf48f99b0bf9d535dcfa2b1a8878b6cc005ae
|
|
BLAKE2b-256 checksum How to use checksums |
fad59d228e333b438fe1ab6262ac9e5349403c20483113757a91087261dbf3d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / aurora_trial-0.0.1-py3-none-any.whl
| Download URL | aurora_trial-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ad90c3166996dc226c2fc87a07ba9fb91903da4ad8f38dec08e64c20757d05b
|
|
BLAKE2b-256 checksum How to use checksums |
9298669d4a5a3b6df987733d3a51c61e123c95172c0f566848888925b76cf707
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for aurora-trial 0.0.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.
