The author of this package has not provided a project description
Metadata
Release files for burst-statsd 0.2.2
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 | |
|---|---|---|---|---|
| burst_statsd-0.2.2.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| burst_statsd-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.8 kB
Release files / burst_statsd-0.2.2.tar.gz
| Download URL | burst_statsd-0.2.2.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69d474f4574862bc09ccc63b0bb75d51e4d1bd0476ed27cdd77bde6b3669d711
|
|
BLAKE2b-256 checksum How to use checksums |
e633cbb53f7225d6cd14c6d9b2bd406d8ff7c072e4621b114170d3ba6bfdbe98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / burst_statsd-0.2.2-py3-none-any.whl
| Download URL | burst_statsd-0.2.2-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8297a53eeea3b1f7291f48805280762030f0f49b1a80d6dc26a5082177e4a539
|
|
BLAKE2b-256 checksum How to use checksums |
84aa908939d5e485b09c32807bd4598f1cd8fb3cbef6e658e7f548f330dec4e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for burst-statsd 0.2.2
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.