The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for refinex-cli 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 | |
|---|---|---|---|---|
| refinex_cli-0.1.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| refinex_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / refinex_cli-0.1.0.tar.gz
| Download URL | refinex_cli-0.1.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
550a4d0d4d49550111c416527e1f05b155fe2284995c713a6eeb95f579b0dd7e
|
|
BLAKE2b-256 checksum How to use checksums |
84b0940909bb7c6f18f13e6eb06b7da935ca4cde56570d2ff8f7824201177455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / refinex_cli-0.1.0-py3-none-any.whl
| Download URL | refinex_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13afb94e05aeef253778e6a089f237fa038b41ac3ce5f7fe8f2de58ca2da4b67
|
|
BLAKE2b-256 checksum How to use checksums |
0497de20314a0a79c89dfd1032ea26e0c9fb3b099cc39e66230485025365ba43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for refinex-cli 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.
