1 maintainer
Metadata
1 maintainer
Release files for codesecdirectmpl2 0.2.0
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 | |
|---|---|---|---|---|
| codesecdirectmpl2-0.2.0.tar.gz | 6.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesecdirectmpl2-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.9 kB
Release files / codesecdirectmpl2-0.2.0.tar.gz
| Download URL | codesecdirectmpl2-0.2.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6cfe6b410a6c3c8543ddcbf0c2ba0c6fd76c3a36db46219f2b67c2da258cd962
|
|
BLAKE2b-256 checksum How to use checksums |
3c28437ebee7944397b291b22e1499a6e4bd20c5b5d80267224244dc73c3a164
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / codesecdirectmpl2-0.2.0-py3-none-any.whl
| Download URL | codesecdirectmpl2-0.2.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47db50a86180f319d0eeadb52193631b7a38cfbc301e0a1dd614a5277e9dd597
|
|
BLAKE2b-256 checksum How to use checksums |
f9b1e6afb558031c36196551bfa9c0ea17226eef32b799b774dbe5aef9aee373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for codesecdirectmpl2 0.2.0
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.
