The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for aqsconverters 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 | |
|---|---|---|---|---|
| aqsconverters-0.1.1.tar.gz | 14.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aqsconverters-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.8 kB
Release files / aqsconverters-0.1.1.tar.gz
| Download URL | aqsconverters-0.1.1.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da4110ed01f17d33a6043d376fa3d88aff9825de2153eb9554d5a66a3950e7f8
|
|
BLAKE2b-256 checksum How to use checksums |
3e30b10e2c34a0e9a3413ec67145e65f2f4d3535d8243a6ee61c57ad08a49b61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / aqsconverters-0.1.1-py3-none-any.whl
| Download URL | aqsconverters-0.1.1-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a088db59824bf1644e22fedb166d26146bbdaf102fd0f09ae250d006f6a3c87
|
|
BLAKE2b-256 checksum How to use checksums |
4475de027803aa2332a10d90b6566ffc3d06b1edcce315f0c8a6836ac138ca91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for aqsconverters 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.
