The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for renku-aqs 1.0.7
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 | |
|---|---|---|---|---|
| renku-aqs-1.0.7.tar.gz | 2.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| renku_aqs-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 MB
Release files / renku-aqs-1.0.7.tar.gz
| Download URL | renku-aqs-1.0.7.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6866e00ce6d5c67dcc12f85c1e78cacf5f9ad344a9fa1cd4e1d4d22cd560ebb8
|
|
BLAKE2b-256 checksum How to use checksums |
ffef5917f827a3bbe75552d85e71d7b62f6d3e5881bd37de6f657a243d03d655
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.5
|
Release files / renku_aqs-1.0.7-py3-none-any.whl
| Download URL | renku_aqs-1.0.7-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29200c77ed14d6caaca5f73948423cb5789d199fc27909219301aa62eab2620f
|
|
BLAKE2b-256 checksum How to use checksums |
9cedbf2b5b1fedb363a254e3d65f0ff711e1d6e4a6edbb1a195efc2846f1c337
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.5
|
Security for renku-aqs 1.0.7
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.
