The author of this package has not provided a project description
Metadata
Release files for zelvanthor-devkit 1.0.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 | |
|---|---|---|---|---|
| zelvanthor_devkit-1.0.0.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zelvanthor_devkit-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 kB
Release files / zelvanthor_devkit-1.0.0.tar.gz
| Download URL | zelvanthor_devkit-1.0.0.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58617651764ad7896267a59558dd43e8fc5eba22459386d5f0bc161d18d564fa
|
|
BLAKE2b-256 checksum How to use checksums |
6ae463cba38677d670be6749585af15f95d7b6a1a66944608d1f99d5fdfafa75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / zelvanthor_devkit-1.0.0-py3-none-any.whl
| Download URL | zelvanthor_devkit-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
daab977eb53e198a528de46259aaeae868c1caadf365f87bee43c5d9451e5940
|
|
BLAKE2b-256 checksum How to use checksums |
1e5d686d6f54123067395c958da6045f3497cb6b8d3101fe44d68b26a31ca086
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for zelvanthor-devkit 1.0.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.