This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for aquaref 0.0.1a1
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 | |
|---|---|---|---|---|
| aquaref-0.0.1a1.tar.gz | 51.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aquaref-0.0.1a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 98.3 kB
Release files / aquaref-0.0.1a1.tar.gz
| Download URL | aquaref-0.0.1a1.tar.gz |
|---|---|
| Size | 51.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa23f3e8203153b9e7835c9895b28475fbd63824702c0461cbfbaaaa6c8452d2
|
|
BLAKE2b-256 checksum How to use checksums |
cec707c3a6c963eb7982bbb5b7f8175fc85ba671d77d9bd3651fc5fdd7118fc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.9.9 Windows/10
|
Release files / aquaref-0.0.1a1-py3-none-any.whl
| Download URL | aquaref-0.0.1a1-py3-none-any.whl |
|---|---|
| Size | 47.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67b015858dee0c09661ebe2e29e7ed00c1372044aaa85e2f3737a8e342aad049
|
|
BLAKE2b-256 checksum How to use checksums |
224b303100605c2826c313afc67d7e65c113ea1a9aa11c2bf1b645aa06b35557
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.9.9 Windows/10
|
Security for aquaref 0.0.1a1
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.
