The author of this package has not provided a project description
3 maintainers
Metadata
3 maintainers
Release files for flaggie 0.99.8
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 | |
|---|---|---|---|---|
| flaggie-0.99.8.tar.gz | 17.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flaggie-0.99.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / flaggie-0.99.8.tar.gz
| Download URL | flaggie-0.99.8.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1078d96922ac7051a2e6750bac830248d4a1b31341a3857ee231ebb28348ed4a
|
|
BLAKE2b-256 checksum How to use checksums |
dcdaa3c6b51f1a4de7ae5b3a5260ba9a3dd9225a2247c4b98c6307f7927e0ec8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / flaggie-0.99.8-py3-none-any.whl
| Download URL | flaggie-0.99.8-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a7100b48f72f7063bda7e4adcbe4c2a355bb37788af5d8d6b1eb3ab9b9573e8
|
|
BLAKE2b-256 checksum How to use checksums |
057d4b0e686494e5f489e06f9c7dd39e55805ce05bae104f44f7d921b1fec207
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for flaggie 0.99.8
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.
