The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-scheduler 1.6.1.7
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.7.tar.gz | 147.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.2 kB
Release files / mns_scheduler-1.6.1.7.tar.gz
| Download URL | mns_scheduler-1.6.1.7.tar.gz |
|---|---|
| Size | 147.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81376f51da486a9120bcf1681e8021d8ad338a05168a2ee47fe3a296722c0cc2
|
|
BLAKE2b-256 checksum How to use checksums |
67cb04d92ba58f0011cda35719f3c079c593e340689040049d77c5ed92351f6b
|
| 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.7-py3-none-any.whl
| Download URL | mns_scheduler-1.6.1.7-py3-none-any.whl |
|---|---|
| Size | 235.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
050c93a607a578127d85f2f9f8c9cc419ce36ad914b888cfde975532c4098710
|
|
BLAKE2b-256 checksum How to use checksums |
d2c2e73cef421e0cf92b7446c1734eea841738dff79839cea0d50dadb1d0c64b
|
| 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.7
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.
