The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.0.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.0.7.tar.gz | 147.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 382.9 kB
Release files / mns_scheduler-1.6.0.7.tar.gz
| Download URL | mns_scheduler-1.6.0.7.tar.gz |
|---|---|
| Size | 147.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ae7722c19bc44a0048efd3856bb0b1a1e89038d2f949f2d44e6e8b15db3747f
|
|
BLAKE2b-256 checksum How to use checksums |
b7542379ed8dfd12fd4d5806cef2006e07f331b97fe8cab67d86a04efe5ac27e
|
| 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.0.7-py3-none-any.whl
| Download URL | mns_scheduler-1.6.0.7-py3-none-any.whl |
|---|---|
| Size | 235.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7093319bc123f0eab2845c23e82b852bcfeec8983fa0ba645fdaa5196b2b237
|
|
BLAKE2b-256 checksum How to use checksums |
35e4ce6be8d812a030986457d53e1fa8f327b0b3f8880d67118c5a9c396dc293
|
| 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.0.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.