The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-common 1.7.3.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.3.6.tar.gz | 165.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_common-1.7.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 450.6 kB
Release files / mns_common-1.7.3.6.tar.gz
| Download URL | mns_common-1.7.3.6.tar.gz |
|---|---|
| Size | 165.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82749af7214350a87d3750ef45c1e5764f3586e27d7ba1b6c61c7c40db872922
|
|
BLAKE2b-256 checksum How to use checksums |
60a733fbec814ba47053c0c79e02e235c6eec7f778e66db306806977f8ffaf3a
|
| 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.3.6-py3-none-any.whl
| Download URL | mns_common-1.7.3.6-py3-none-any.whl |
|---|---|
| Size | 285.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf73cb517bee74cf994df6e13d4fd6386b35cc8827b1e26f848c3b23f62062cf
|
|
BLAKE2b-256 checksum How to use checksums |
1efa6b7b12eca1446e4e1e7b77cf6699b1cc9b687371e3377cc9a883729b1dd8
|
| 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.3.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.
