The author of this package has not provided a project description
Metadata
Release files for mns-scheduler 1.6.0.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.0.8.tar.gz | 147.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_scheduler-1.6.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 382.8 kB
Release files / mns_scheduler-1.6.0.8.tar.gz
| Download URL | mns_scheduler-1.6.0.8.tar.gz |
|---|---|
| Size | 147.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cccbbf576805c08a1d3d2071173042f98a25b70bd49b7d6c0a8d938737c639f0
|
|
BLAKE2b-256 checksum How to use checksums |
d74268eef43770b4695f34f6a3424b7aa5e726fc65f921c10d17b4514967ded7
|
| 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.8-py3-none-any.whl
| Download URL | mns_scheduler-1.6.0.8-py3-none-any.whl |
|---|---|
| Size | 235.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c6e73576f6e6a2d8293cfdbb38221b4ec6f8b03e2c913a7a3bd45b10234d244
|
|
BLAKE2b-256 checksum How to use checksums |
f87e58af4bef78f780fd070551c2c00875af707316ce2724c9b9d1cd919443dd
|
| 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.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.