The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for atesy 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 | |
|---|---|---|---|---|
| atesy-0.1.0.tar.gz | 864 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atesy-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 kB
Release files / atesy-0.1.0.tar.gz
| Download URL | atesy-0.1.0.tar.gz |
|---|---|
| Size | 864 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9506a72aa227e65b7bfd849ab6db5d5783eea5775c0a40745f96f4bb914ef39e
|
|
BLAKE2b-256 checksum How to use checksums |
62c129ebb727baeea99bf3d7e216d42f1c13f3fa493dcc5deb2a1dd0977378d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.5 CPython/3.6.8 Windows/10
|
Release files / atesy-0.1.0-py3-none-any.whl
| Download URL | atesy-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3035de0c26d7539a9e393468ef352664be52fa5b52d557416884e8355af777a3
|
|
BLAKE2b-256 checksum How to use checksums |
870893c3cca8e159c3891e694beb97bb299cf078c8d17d58abd22600543ebb81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.5 CPython/3.6.8 Windows/10
|
Security for atesy 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.
