The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.0.6
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.6.tar.gz | 145.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 378.3 kB
Release files / mns_scheduler-1.6.0.6.tar.gz
| Download URL | mns_scheduler-1.6.0.6.tar.gz |
|---|---|
| Size | 145.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e92ab3ead6038d9f98abf2cb0340fd0ee9c61c461c996d5291023a597e52fab8
|
|
BLAKE2b-256 checksum How to use checksums |
a439b0440bddf5203fcdc6b8b1aa14ba9d83e1a4ae96b5d91720557c05ff119f
|
| 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.6-py3-none-any.whl
| Download URL | mns_scheduler-1.6.0.6-py3-none-any.whl |
|---|---|
| Size | 232.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4194137069448c691672e29dc66d542915032b196ed9deab18c16ec8492868f2
|
|
BLAKE2b-256 checksum How to use checksums |
d27d7fb1c9781d96fcee6df125b79c62c3aa6e606338973527e759b21932c5cc
|
| 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.6
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.