1 maintainer
Metadata
1 maintainer
Release files for codesecdirectgpl3 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 | |
|---|---|---|---|---|
| codesecdirectgpl3-0.1.0.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesecdirectgpl3-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.7 kB
Release files / codesecdirectgpl3-0.1.0.tar.gz
| Download URL | codesecdirectgpl3-0.1.0.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6de0404e389080aef7a294a3067e4299e774eb6b784f9a0d58942d536967e198
|
|
BLAKE2b-256 checksum How to use checksums |
bf70242c14bdd1e5ea9efcf5f9c77f262ba5b36a2f4c580ad9530cccb21c217b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / codesecdirectgpl3-0.1.0-py3-none-any.whl
| Download URL | codesecdirectgpl3-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
280b851c4d620eafad7e14ba80fab91c9b7ebf2faad9fdab1b8c5267cc58b6b1
|
|
BLAKE2b-256 checksum How to use checksums |
f55bb81760b71272c2c51ec95327569f711deb443c268d3026312036640c7e37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for codesecdirectgpl3 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.
