The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pyreinst 0.0.1
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 | |
|---|---|---|---|---|
| pyreinst-0.0.1.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyreinst-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.3 kB
Release files / pyreinst-0.0.1.tar.gz
| Download URL | pyreinst-0.0.1.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
114a236e4d84c5d3758f6d0fa9bb161c0cf7cff60ae7aedbf7eab69b282c1451
|
|
BLAKE2b-256 checksum How to use checksums |
1bd156084ce61e3325a9d3b7917db91253a997cee9301fc1c7e6288ac9a8cd69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Release files / pyreinst-0.0.1-py3-none-any.whl
| Download URL | pyreinst-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99630b6f6481d1cd0eb9d7059dc34969f3d7c64874f0d46fdda65d256b94bff6
|
|
BLAKE2b-256 checksum How to use checksums |
cf3026e15f887466c8f56daa764c9786f577acf435bca394a98ec67bfbd21912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Security for pyreinst 0.0.1
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.
