The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pyroast 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 | |
|---|---|---|---|---|
| PyROAST-0.1.0.tar.gz | 865 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| PyROAST-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / PyROAST-0.1.0.tar.gz
| Download URL | PyROAST-0.1.0.tar.gz |
|---|---|
| Size | 865 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5b0133fe1c12b0814375e9cc746e9ee15710a4496ace0409e29cc47bbebc1db
|
|
BLAKE2b-256 checksum How to use checksums |
49b47f005d6020d2d0bbad2e97c95bfd97d0dd10083f567f8201f016b38f2d39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.2 CPython/3.8.4 Linux/5.4.0-42-generic
|
Release files / PyROAST-0.1.0-py3-none-any.whl
| Download URL | PyROAST-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5704081f74f9747edc502febbe10b0f349585476f7af380bd8f324852857d89c
|
|
BLAKE2b-256 checksum How to use checksums |
9e5ef88e8e63418e29cb07f64d4127428f9a0e34f41a8473694b19af41f0eab3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.2 CPython/3.8.4 Linux/5.4.0-42-generic
|
Security for pyroast 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.
