The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pyrefra 26.10.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 | |
|---|---|---|---|---|
| pyrefra-26.10.1.tar.gz | 333.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyrefra-26.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 673.4 kB
Release files / pyrefra-26.10.1.tar.gz
| Download URL | pyrefra-26.10.1.tar.gz |
|---|---|
| Size | 333.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8691fdd4223bf72f7314ee4a342aba82bc14b630f584a18a3431515fb1e3e2f
|
|
BLAKE2b-256 checksum How to use checksums |
52398028d4f25a7a5a388867d920a4488da1ca44f99cc170b957d4b641a0ac0f
|
| 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.1-py3-none-any.whl
| Download URL | pyrefra-26.10.1-py3-none-any.whl |
|---|---|
| Size | 340.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72d482390a2bb37d0fa5edbf7976035cb2cc9c38bd79e6304a81eddf33d99220
|
|
BLAKE2b-256 checksum How to use checksums |
fe0d6316bad9b566fcd09264fc4042bcffd97c6a87d5793139614ec79da0e850
|
| 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.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.
