The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.2.1
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.1.tar.gz | 146.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 381.6 kB
Release files / mns_scheduler-1.6.2.1.tar.gz
| Download URL | mns_scheduler-1.6.2.1.tar.gz |
|---|---|
| Size | 146.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f49429d4c6dc8366635e1210a37a67e45886dc150b5f900959268a3bae664794
|
|
BLAKE2b-256 checksum How to use checksums |
d42801b49829ce096a09e7482c7eab97c9983f8665266730b273f11f30f5a6a9
|
| 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.1-py3-none-any.whl
| Download URL | mns_scheduler-1.6.2.1-py3-none-any.whl |
|---|---|
| Size | 234.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab18be3558b4f2b12540f0b4dcd748f180c3184e8ee4481b76d744df80032473
|
|
BLAKE2b-256 checksum How to use checksums |
df8e4367aa63dcff8cb06302df873793ecbc4502d1d1812f528061ad7d2f6cd1
|
| 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.1
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.