The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.2.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.2.5.tar.gz | 148.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 385.3 kB
Release files / mns_scheduler-1.6.2.5.tar.gz
| Download URL | mns_scheduler-1.6.2.5.tar.gz |
|---|---|
| Size | 148.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28e10af8576f03d5aad39e5156376725f4ad55c041507724e402f55a1a938aba
|
|
BLAKE2b-256 checksum How to use checksums |
ebdfb5bbcae963f931fef42db06e0b0fd5ecb32bb86229171dd4093871341e2c
|
| 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.2.5-py3-none-any.whl
| Download URL | mns_scheduler-1.6.2.5-py3-none-any.whl |
|---|---|
| Size | 236.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85db7e26c617201f151141714721f819d81645fb2c7e07f6fe6066083f7640c1
|
|
BLAKE2b-256 checksum How to use checksums |
8bdb359eb6448bd684790313c0ce184e4fcd3cc02f7bb8efdc13aeb102ae45da
|
| 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.2.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.