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