The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pyrefra 26.10.2
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 | |
|---|---|---|---|---|
| pyrefra-26.10.2.tar.gz | 333.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyrefra-26.10.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 673.8 kB
Release files / pyrefra-26.10.2.tar.gz
| Download URL | pyrefra-26.10.2.tar.gz |
|---|---|
| Size | 333.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
780243298f996d37dc967bf5edd607df55f3804d622967de1a73da3b3204b5bd
|
|
BLAKE2b-256 checksum How to use checksums |
db256bb50173ebdb0cb5f8c20d71f0295da8fd8f37596355073867bf9a82339f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / pyrefra-26.10.2-py3-none-any.whl
| Download URL | pyrefra-26.10.2-py3-none-any.whl |
|---|---|
| Size | 340.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7143e43893d0e3f0c091ad4d51380d1a465a2bb1a54a201062d2c4a41ed1bacc
|
|
BLAKE2b-256 checksum How to use checksums |
0be9b2d20bc7d6e528815b8a2d4a056ee95a34b3e36e66ac7804a72ec1384d7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for pyrefra 26.10.2
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.
