The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mns-common 1.7.3.5
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.5.tar.gz | 163.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mns_common-1.7.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.4 kB
Release files / mns_common-1.7.3.5.tar.gz
| Download URL | mns_common-1.7.3.5.tar.gz |
|---|---|
| Size | 163.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb527188dedd3a179174db3dff756382fa77ca087315f022365bc27ce22b82d6
|
|
BLAKE2b-256 checksum How to use checksums |
af01a81d2af034c22f69525e9983eb18f4535e1ecdbfafeb3090aec92c5bdf08
|
| 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.5-py3-none-any.whl
| Download URL | mns_common-1.7.3.5-py3-none-any.whl |
|---|---|
| Size | 282.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d6403d1bbd481fac3a6a17ab4937440e90091b8a52f5c29799d33c103650bf1
|
|
BLAKE2b-256 checksum How to use checksums |
c2c8cfabc45644877f952236ee438212685fa5e40d726a3683ef917faacdf1f1
|
| 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.5
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.
