The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.2.0
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.0.tar.gz | 147.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.8 kB
Release files / mns_scheduler-1.6.2.0.tar.gz
| Download URL | mns_scheduler-1.6.2.0.tar.gz |
|---|---|
| Size | 147.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31d7d90e0c144ff33827222975e705abd97f2213f36870695c87467275ce3672
|
|
BLAKE2b-256 checksum How to use checksums |
8e91fc1b69a0ed345f9cd8a2f8b7d64f1384b5e6faec23e8e908be4fad6b11c2
|
| 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.0-py3-none-any.whl
| Download URL | mns_scheduler-1.6.2.0-py3-none-any.whl |
|---|---|
| Size | 236.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9ff0e26393c1dfc4916021e677bed72ccb46f0d019b49470c1fcb5e229fd708
|
|
BLAKE2b-256 checksum How to use checksums |
f812546622527c617320e08d0d47c010dd13bc197a33886c7e5f2e9fed706463
|
| 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.0
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.