2 maintainers
Metadata
2 maintainers
Release files for bits-slack 2.0.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 | |
|---|---|---|---|---|
| bits_slack-2.0.0.tar.gz | 8.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bits_slack-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / bits_slack-2.0.0.tar.gz
| Download URL | bits_slack-2.0.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83d8b6b1806ceed82bb7a87388d2c5af4bcbc5d9791c5915e9de5d9af9c6580a
|
|
BLAKE2b-256 checksum How to use checksums |
64be9963dd156ef4bf390da71177068b8825d45764f572b71bfedcceba79cf2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.4 CPython/3.12.3 Linux/6.17.0-1010-azure
|
Release files / bits_slack-2.0.0-py3-none-any.whl
| Download URL | bits_slack-2.0.0-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a68fd9360e203d33c020e7bad272e81475db1269eee7d95a5410f047703a4b9
|
|
BLAKE2b-256 checksum How to use checksums |
158d43cde0073e7bb76d25d8bc3192568d3858b7c035aafed27384243b2683f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.4 CPython/3.12.3 Linux/6.17.0-1010-azure
|
Security for bits-slack 2.0.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.
