The author of this package has not provided a project description
Metadata
Release files for slack-sansio 1.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 | |
|---|---|---|---|---|
| slack-sansio-1.1.0.tar.gz | 26.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slack_sansio-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.9 kB
Release files / slack-sansio-1.1.0.tar.gz
| Download URL | slack-sansio-1.1.0.tar.gz |
|---|---|
| Size | 26.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dec16e6f9ced6003de201c5e3bd1dbfc053ab8c8772ab29529772805b8a18a1
|
|
BLAKE2b-256 checksum How to use checksums |
8bdd76c06749f4bed88a7eed7aca8d013584d1c91d3e9c8f961534553c213fd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.7.1 Linux/4.15.0-1028-gcp
|
Release files / slack_sansio-1.1.0-py3-none-any.whl
| Download URL | slack_sansio-1.1.0-py3-none-any.whl |
|---|---|
| Size | 38.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0403c02ba6c3e57f6de7e9522aef7973bd71e33453f5b2ea760ec513b619750a
|
|
BLAKE2b-256 checksum How to use checksums |
e62fe5c499327ede58d13a907fa728a90466cba5ea942db95fd53f018e8c4dca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.7.1 Linux/4.15.0-1028-gcp
|
Security for slack-sansio 1.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.