The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.1.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.1.9.tar.gz | 147.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.8 kB
Release files / mns_scheduler-1.6.1.9.tar.gz
| Download URL | mns_scheduler-1.6.1.9.tar.gz |
|---|---|
| Size | 147.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1b7c352e668adbe04edd7abb21c8c1097e23a5148656e8c1f84f1b7d46aec79
|
|
BLAKE2b-256 checksum How to use checksums |
d61b30bd87dca49cc6c588ed8839289a79e8aede5ecea05d5478af5166656852
|
| 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.9-py3-none-any.whl
| Download URL | mns_scheduler-1.6.1.9-py3-none-any.whl |
|---|---|
| Size | 236.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4681049c45eda14f98f4df465c5cb761b4b5fb5c404a0e940dbab5c7cd09b699
|
|
BLAKE2b-256 checksum How to use checksums |
baa94da17fefdbe6e4c78a2aa789905b8df8434d09277e2e578977348db757f2
|
| 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.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.