1 maintainer
Metadata
1 maintainer
Release files for netk-nuklear 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 | |
|---|---|---|---|---|
| netk_nuklear-0.1.0.tar.gz | 227.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| netk_nuklear-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 456.1 kB
Release files / netk_nuklear-0.1.0.tar.gz
| Download URL | netk_nuklear-0.1.0.tar.gz |
|---|---|
| Size | 227.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2cfed3da147bfe5165d3393114a185c15b32d49415fb7abb3e7886e7d4f0e57
|
|
BLAKE2b-256 checksum How to use checksums |
66f5ee952fb4339adf54e1a056722a2f97e85637d7f39db31300e8f457527ee8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.10.11 Windows/10
|
Release files / netk_nuklear-0.1.0-py3-none-any.whl
| Download URL | netk_nuklear-0.1.0-py3-none-any.whl |
|---|---|
| Size | 228.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2637152c6aca2457f5a32368b19fca0fc014cbc61b9b01664629e49f0626a1a
|
|
BLAKE2b-256 checksum How to use checksums |
e9b12868428834fd89bfea31dbc8bc72ebfa228404956a3654cbe44834b9617a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.10.11 Windows/10
|
Security for netk-nuklear 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.
