1 maintainer
Metadata
1 maintainer
Release files for codesecindirectmitgpl3 0.1.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 | |
|---|---|---|---|---|
| codesecindirectmitgpl3-0.1.0.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesecindirectmitgpl3-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / codesecindirectmitgpl3-0.1.0.tar.gz
| Download URL | codesecindirectmitgpl3-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62f85fa571cd65c3604173b19f8579d5177777851b8635077fc60001dff61bcd
|
|
BLAKE2b-256 checksum How to use checksums |
fb78f7635b7dc1a72da003c34a63dbc7a052b25b26e9b081bf94c8e1190474d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / codesecindirectmitgpl3-0.1.0-py3-none-any.whl
| Download URL | codesecindirectmitgpl3-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8ce000b2e24de7b564c8d6257a580ca7b10085638ed3e0e3d809ab9ce7c3053
|
|
BLAKE2b-256 checksum How to use checksums |
2202c5cd2b1254c9f8f30373d3ed17d5368eca2ccf651ba688d376dce3950ad8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for codesecindirectmitgpl3 0.1.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.
