The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.1.5
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 | |
|---|---|---|---|---|
| mns_scheduler-1.6.1.5.tar.gz | 147.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.1 kB
Release files / mns_scheduler-1.6.1.5.tar.gz
| Download URL | mns_scheduler-1.6.1.5.tar.gz |
|---|---|
| Size | 147.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
544748ae6ce2cff1d1f97fa7e1d36d048baced09f09a131e5e7f7b9c999d3c0e
|
|
BLAKE2b-256 checksum How to use checksums |
d4b883d5b7d7a5f668be0fbc1fb05aac35fb3257abc3b80a57d2607941e91890
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Release files / mns_scheduler-1.6.1.5-py3-none-any.whl
| Download URL | mns_scheduler-1.6.1.5-py3-none-any.whl |
|---|---|
| Size | 235.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80d1058ef396e8ff0511642269e39f6e113d5a154f245ee536a2384eae315d9c
|
|
BLAKE2b-256 checksum How to use checksums |
a72fe433c4c6dd872597172a3e95190165dea312cf59a7b6ea8d97add799a1ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Security for mns-scheduler 1.6.1.5
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.