1 maintainer
Metadata
1 maintainer
Release files for reflex-xpw-backend 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_backend-0.3.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reflex_xpw_backend-0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.9 kB
Release files / reflex_xpw_backend-0.3.tar.gz
| Download URL | reflex_xpw_backend-0.3.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38bc768c27a03443f406020d730178c033bd55c339bb6f36cc9767f3602ea00b
|
|
BLAKE2b-256 checksum How to use checksums |
2e1959ca438278cae9da96255e290762379cc944da854b7f1a4e85358a4bc75b
|
| 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_backend-0.3-py3-none-any.whl
| Download URL | reflex_xpw_backend-0.3-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56291eae496514e8c9e89ef29c453a7c0a90dd5341379659f57eda9f233ae3b6
|
|
BLAKE2b-256 checksum How to use checksums |
d73bcc51d4c6380ceb20aa74d2410487a26044403ccf692d54d7efb673dd6b3e
|
| 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-backend 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.
