The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.2.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.2.3.tar.gz | 147.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 382.0 kB
Release files / mns_scheduler-1.6.2.3.tar.gz
| Download URL | mns_scheduler-1.6.2.3.tar.gz |
|---|---|
| Size | 147.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4bfe6e4d3f58217a9855905a00f52f36238cdcfc06a880ec6c248f4ed4622ddb
|
|
BLAKE2b-256 checksum How to use checksums |
d751bd16ada7e86c95773cfe98def868fe394446a94cda484a42ae7c2f779023
|
| 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.3-py3-none-any.whl
| Download URL | mns_scheduler-1.6.2.3-py3-none-any.whl |
|---|---|
| Size | 234.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71384ac0c2ce70dd12e16a6959e374754011237ff33fbf26acf82949572d69a1
|
|
BLAKE2b-256 checksum How to use checksums |
168d8503623c2dee9f7c5099c69849aff08874a9f285c0d2f286a177cee2d551
|
| 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.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.