The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-common 1.7.3.1
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.1.tar.gz | 163.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_common-1.7.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.2 kB
Release files / mns_common-1.7.3.1.tar.gz
| Download URL | mns_common-1.7.3.1.tar.gz |
|---|---|
| Size | 163.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a32cfcee6d6f2555d08e2844ff7f84ab58840bb6349f9689965389f70f9f8243
|
|
BLAKE2b-256 checksum How to use checksums |
93f129d2fc3eb4e4bb2839f52564ac6c253c28fcb0f8d2122c20797f6f3d0624
|
| 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.1-py3-none-any.whl
| Download URL | mns_common-1.7.3.1-py3-none-any.whl |
|---|---|
| Size | 282.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40bae465a8915c773dc5932d302753c82d429b2621a10d0382bde275e8965560
|
|
BLAKE2b-256 checksum How to use checksums |
d2e3ad86676f92fc2d3b58b2f4cabd1e60717f244bb448d3ded248b7abaa37bc
|
| 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.1
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.
