The author of this package has not provided a project description
Metadata
Release files for mongo-statsd 1.0.6
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 | |
|---|---|---|---|---|
| mongo_statsd-1.0.6.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mongo_statsd-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / mongo_statsd-1.0.6.tar.gz
| Download URL | mongo_statsd-1.0.6.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
512c8000b65e953fe2b75d4854234b4376bc553abc26eacc3732be9584d7906b
|
|
BLAKE2b-256 checksum How to use checksums |
5daac577c4361713c2c9885996f97d55e12b8bb900f1aa3f3c0cd32cf888dde4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / mongo_statsd-1.0.6-py3-none-any.whl
| Download URL | mongo_statsd-1.0.6-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4885e0155f2de0a24e9058578f7fe4bf14b0d23288f0376bb731e65b910a2ca1
|
|
BLAKE2b-256 checksum How to use checksums |
25e9e36323b3168f994d6ab8645dce0104726e7774ede2b9c7a5f6d8f67c4be2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for mongo-statsd 1.0.6
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.