The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for beespammer 4.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 | |
|---|---|---|---|---|
| beespammer-4.0.0.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beespammer-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / beespammer-4.0.0.tar.gz
| Download URL | beespammer-4.0.0.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31b6dff67609b66030fe76d7be7e4bc5c85a3f324c8aa0cd0a720666113a6c6f
|
|
BLAKE2b-256 checksum How to use checksums |
c2169772beaa4cf3d453b4cf665f33dbd990d8739b81af12842788666ecc6fb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.7 CPython/3.9.6 Linux/5.13.10-arch1-1
|
Release files / beespammer-4.0.0-py3-none-any.whl
| Download URL | beespammer-4.0.0-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c09e04ba2c5085e3140f3483833a6c1a9938c1751957603fb12d78da0fc3f1ab
|
|
BLAKE2b-256 checksum How to use checksums |
bc8d48c04caed58f81d60e8d41e71072875d909e3637dc1701f699a421bfcfe3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.7 CPython/3.9.6 Linux/5.13.10-arch1-1
|
Security for beespammer 4.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.
