Metadata
Release files for flara 0.0.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 | |
|---|---|---|---|---|
| flara-0.0.1.tar.gz | 969 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flara-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / flara-0.0.1.tar.gz
| Download URL | flara-0.0.1.tar.gz |
|---|---|
| Size | 969 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88e92b6d5fd2c966715cbd83a7125261eee1826fc281a587b6f2a82c348a02eb
|
|
BLAKE2b-256 checksum How to use checksums |
a283bae966a09ec5185a249fbae7f912d5036a5ca83ae04127f25d83d3ff79b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Release files / flara-0.0.1-py3-none-any.whl
| Download URL | flara-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50d4151c73a8d1dd81a7e9fd79b4ae55f9c78bf0a885e5e06dbb318f25131085
|
|
BLAKE2b-256 checksum How to use checksums |
7614c591ba139d9bac12959b61346561743c87390b9c1780b46512e68a2dacf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.18.4 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Security for flara 0.0.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.