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