The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for nxrunner 1.0.3
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 | |
|---|---|---|---|---|
| nxrunner-1.0.3.tar.gz | 61.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nxrunner-1.0.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 132.9 kB
Release files / nxrunner-1.0.3.tar.gz
| Download URL | nxrunner-1.0.3.tar.gz |
|---|---|
| Size | 61.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7be77682276d8f077538be674f3ea7cc8c18532c68c03582102d9c124aa142ed
|
|
BLAKE2b-256 checksum How to use checksums |
21e626124557aaaf5e031b7ae9014fa2bf26592b86f03dc706ccc3fec7b96847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.3
|
Release files / nxrunner-1.0.3-py2.py3-none-any.whl
| Download URL | nxrunner-1.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 71.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ae101916d06c24bc3f4163a09e221251d177ea3f6237689b023c9be644c5f408
|
|
BLAKE2b-256 checksum How to use checksums |
dab38d3be584c8da01bf7a98d3c70ac39f639c4dadf85f22fb611c23a08e1ef8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.3
|
Security for nxrunner 1.0.3
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.
