The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for buzz-agent 1.2.4
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 | |
|---|---|---|---|---|
| buzz_agent-1.2.4.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| buzz_agent-1.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.6 kB
Release files / buzz_agent-1.2.4.tar.gz
| Download URL | buzz_agent-1.2.4.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8660f537f362de7f75a530a717384f793c0439cc44042757b6c0d704fc7ec497
|
|
BLAKE2b-256 checksum How to use checksums |
641261cbc50ed0ab309a3f02eb97ccbf34afca2d0c7c1898fa8d4ed3eaaa4443
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / buzz_agent-1.2.4-py3-none-any.whl
| Download URL | buzz_agent-1.2.4-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae701a542f1c03fdcd9182e7f54005cf9e6bb8525ed9d5194853e28fd93d2727
|
|
BLAKE2b-256 checksum How to use checksums |
2a0ab80ef15f1385c8ff999c9fada07c065bb5b762d82623a5ee9a9738418f15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for buzz-agent 1.2.4
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.
