The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.0.9
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.0.9.tar.gz | 147.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.0 kB
Release files / mns_scheduler-1.6.0.9.tar.gz
| Download URL | mns_scheduler-1.6.0.9.tar.gz |
|---|---|
| Size | 147.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcc5e5f1a283631385cfdbde529f1a2123606101a9e21165504d2f8193576278
|
|
BLAKE2b-256 checksum How to use checksums |
5e52babf4e1973a47066ff24a577dfdb1ad36d0954440afe7e8b69479d100618
|
| 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.0.9-py3-none-any.whl
| Download URL | mns_scheduler-1.6.0.9-py3-none-any.whl |
|---|---|
| Size | 235.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8d7cef7dbcc243f7dea8bc8cb587ac7bbb4a2dc951b66d79a8985c3be8a1981
|
|
BLAKE2b-256 checksum How to use checksums |
5af5b81bdd4ef8e2f5eb4ee9b17237bf225632f242554b999529cf0914ad8275
|
| 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.0.9
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.