1 maintainer
Metadata
1 maintainer
Release files for codesecdirectagpl3 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 | |
|---|---|---|---|---|
| codesecdirectagpl3-0.2.0.tar.gz | 13.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesecdirectagpl3-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.0 kB
Release files / codesecdirectagpl3-0.2.0.tar.gz
| Download URL | codesecdirectagpl3-0.2.0.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e5fade281b696e3d4a9b0116e76d3cd43fa51bcd3323740ae81971c48127801
|
|
BLAKE2b-256 checksum How to use checksums |
19ae1fb4b2a5b3220f0574f38bd3f7f831ea0649ca578b8dc93d1e4dcc56f329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / codesecdirectagpl3-0.2.0-py3-none-any.whl
| Download URL | codesecdirectagpl3-0.2.0-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
408f0388d3ce8ffb7ff42e5fa04a4d22476758599e6ad27ed7274032de306fd7
|
|
BLAKE2b-256 checksum How to use checksums |
3b3272a0fd304ed8f2747e8e1d5d8bd9b9ae9a47098835cdfc4cb28bb2d92ac6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for codesecdirectagpl3 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.
