1 maintainer
Metadata
1 maintainer
Release files for redcaptcha-challenger 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 | |
|---|---|---|---|---|
| redcaptcha_challenger-0.0.1.tar.gz | 16.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| redcaptcha_challenger-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.8 kB
Release files / redcaptcha_challenger-0.0.1.tar.gz
| Download URL | redcaptcha_challenger-0.0.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c470db76d93438dd1c46ef66b23aec9535f7bbefeee2e4b7d920018bcfd62dcd
|
|
BLAKE2b-256 checksum How to use checksums |
95d2a1284363e743f9e0e1f9ad83309c2ed35acaa335fe618eb9492b85bc0002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Release files / redcaptcha_challenger-0.0.1-py3-none-any.whl
| Download URL | redcaptcha_challenger-0.0.1-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe00f26e1e9cb09031dfb5234fb94957ec7301d731730c50ce372b919ae52166
|
|
BLAKE2b-256 checksum How to use checksums |
04bc8ce8ecd0801b1a492ec7f686cecb3951c4a9cebfee356520c1c32781fbf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Security for redcaptcha-challenger 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.
