The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.1.3
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.3.tar.gz | 147.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.0 kB
Release files / mns_scheduler-1.6.1.3.tar.gz
| Download URL | mns_scheduler-1.6.1.3.tar.gz |
|---|---|
| Size | 147.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a6812d495a8a64a8f333ae933adb1cd0dd4986a90e0fe67e17595517a5a86df
|
|
BLAKE2b-256 checksum How to use checksums |
51accecccbe7f8d576ac6d4dbff097e5f1bab3671ed57e0b6dbd14ca7948fe2e
|
| 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.3-py3-none-any.whl
| Download URL | mns_scheduler-1.6.1.3-py3-none-any.whl |
|---|---|
| Size | 235.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2ac052ec487a3c7f118f42e3e5745a5b08cdfd765acffb321f53c4a26c032ae
|
|
BLAKE2b-256 checksum How to use checksums |
84da2d7ae2229dcdd399773fb402c66019b7c003a20cfa4e80206e273f2140b2
|
| 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.3
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.