CMS Monitoring utilities
1 maintainer
Metadata
1 maintainer
Release files for CMSMonitoring 0.6.13
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 | |
|---|---|---|---|---|
| cmsmonitoring-0.6.13.tar.gz | 33.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cmsmonitoring-0.6.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.1 kB
Release files / cmsmonitoring-0.6.13.tar.gz
| Download URL | cmsmonitoring-0.6.13.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3350bc0f2228e5aaf0c500358391ad53869acf1cbaeba51cc506aebbc9a6016
|
|
BLAKE2b-256 checksum How to use checksums |
7016a97af06bd4f293c7280afa3a1f6706e06c766803376bd33f9a327e9efdfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Release files / cmsmonitoring-0.6.13-py3-none-any.whl
| Download URL | cmsmonitoring-0.6.13-py3-none-any.whl |
|---|---|
| Size | 41.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
61b60848994b99e67f09a7545a173b31bd97e5f94578b492c7a140b594106fc0
|
|
BLAKE2b-256 checksum How to use checksums |
63f696d3ef07da6dc7c4ba84822b8815482b76f143722bb729527974cfdfdcce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for CMSMonitoring 0.6.13
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.
