The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.1.8
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.8.tar.gz | 147.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.6 kB
Release files / mns_scheduler-1.6.1.8.tar.gz
| Download URL | mns_scheduler-1.6.1.8.tar.gz |
|---|---|
| Size | 147.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b44214f5b08528d7f50fbdbcc72a59c11e27e5ac637b7b64b528f7c3f90852d0
|
|
BLAKE2b-256 checksum How to use checksums |
99ab9e73c3164502d35e2c7cb54559f4c416e276f879cd583f383321fc5d45f3
|
| 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.8-py3-none-any.whl
| Download URL | mns_scheduler-1.6.1.8-py3-none-any.whl |
|---|---|
| Size | 235.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b493342fc80974e569fc6bb3063e67d7d15184b0e9392cf217771a36483ccbd
|
|
BLAKE2b-256 checksum How to use checksums |
f4710172cde545a37dc3c261c9b0c8cb52a0171d54034240338feb62c41b621b
|
| 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.8
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.