The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-common 1.7.3.4
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.4.tar.gz | 163.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_common-1.7.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.3 kB
Release files / mns_common-1.7.3.4.tar.gz
| Download URL | mns_common-1.7.3.4.tar.gz |
|---|---|
| Size | 163.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13baaf4e169aaa9fade588714f7e3a77cb0a0e2de85fcee6b5a51cb121cba20c
|
|
BLAKE2b-256 checksum How to use checksums |
07e52987bb4ece2e089ba6a3806addb43a2a7736e01344130349a695c64e19ac
|
| 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.4-py3-none-any.whl
| Download URL | mns_common-1.7.3.4-py3-none-any.whl |
|---|---|
| Size | 282.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02dbd4553ad201ddf0d73a5ddb67a7a99b30e335ec6ecbcb6a3cce2897dc81a2
|
|
BLAKE2b-256 checksum How to use checksums |
86706d1379553a9297adb375ec2457a0de65be63fca4a98a7864b5e8c69a6534
|
| 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.4
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.
