The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for flask-chest 0.0.10
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 | |
|---|---|---|---|---|
| flask-chest-0.0.10.tar.gz | 7.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flask_chest-0.0.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.8 kB
Release files / flask-chest-0.0.10.tar.gz
| Download URL | flask-chest-0.0.10.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
980e1b719086c66ee3163b230c3403f464f439800f10f6761b358b59659687b9
|
|
BLAKE2b-256 checksum How to use checksums |
edb8145c9244d26a9a4b7dfbf36fdad0fd0b9e9adfe88efbc362cd5977949408
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.4
|
Release files / flask_chest-0.0.10-py3-none-any.whl
| Download URL | flask_chest-0.0.10-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
761394e7cf92d1cc81c2678baeba474dfac188ed663b6cb4f46095690521ad0f
|
|
BLAKE2b-256 checksum How to use checksums |
531d1f7ce336e9d1a8649c28259c53c042acbac855acd494e31c93e6a0033694
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.4
|
Security for flask-chest 0.0.10
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.
