1 maintainer
Metadata
1 maintainer
Release files for reflex-xpw-frontend 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 | |
|---|---|---|---|---|
| reflex_xpw_frontend-0.3.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reflex_xpw_frontend-0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.1 kB
Release files / reflex_xpw_frontend-0.3.tar.gz
| Download URL | reflex_xpw_frontend-0.3.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f4693a9fbec45310a368fe0c97f45c2c1e4654155a3c96a39618568b41611e8
|
|
BLAKE2b-256 checksum How to use checksums |
9a98a951489cf7d5ba1457f640abe34c3e9c550c47be92b78c7eb469bcca8930
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / reflex_xpw_frontend-0.3-py3-none-any.whl
| Download URL | reflex_xpw_frontend-0.3-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b5f7136b0ad4fde9ebac8a2fb844628be93ad2abbd09d1b528b33617dcc47ae
|
|
BLAKE2b-256 checksum How to use checksums |
f672c5d83278d1b8469ee5fb516fc0614be4850ba8aa57e8848f7d561f62dd13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for reflex-xpw-frontend 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.
