The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-common 1.7.4.6
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_common-1.7.4.6.tar.gz | 165.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_common-1.7.4.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 450.3 kB
Release files / mns_common-1.7.4.6.tar.gz
| Download URL | mns_common-1.7.4.6.tar.gz |
|---|---|
| Size | 165.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86cb3805aedee9b33dd5a613ce1fed36b0fb6fc00dfd61a6e6766265cea4bff5
|
|
BLAKE2b-256 checksum How to use checksums |
41695fe1bd8d075ee85e42303d94dc8eb690c72e2cb587730c291aa3d8f5e1bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Release files / mns_common-1.7.4.6-py3-none-any.whl
| Download URL | mns_common-1.7.4.6-py3-none-any.whl |
|---|---|
| Size | 284.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e730a9907afac97f3ad55d920fd85feacc279e0501dffd1b909168977737b11
|
|
BLAKE2b-256 checksum How to use checksums |
e8efec8f8dca4c7c606e3b1caff3e00c3d986f0a56bfa5f41856b09f14ae98ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Security for mns-common 1.7.4.6
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.
