Ideally, this inhales a lot of media and regurgitates markdown for a curated, research repository.
1 maintainer
Metadata
1 maintainer
Release files for arkeo 0.2.6
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 | |
|---|---|---|---|---|
| arkeo-0.2.6.tar.gz | 71.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arkeo-0.2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 176.3 kB
Release files / arkeo-0.2.6.tar.gz
| Download URL | arkeo-0.2.6.tar.gz |
|---|---|
| Size | 71.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
451bb1cc21245c34872c69f3162ed8b09ea98cbe76201f14957e40325f8cff95
|
|
BLAKE2b-256 checksum How to use checksums |
e2f6efac90e1b2f09f24f35875a00772cb706bcca187059912959f8a46543adb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / arkeo-0.2.6-py3-none-any.whl
| Download URL | arkeo-0.2.6-py3-none-any.whl |
|---|---|
| Size | 104.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24b8ef48f7b203e6d6409725921b965b09d065c4f07b681b7231453c850ba849
|
|
BLAKE2b-256 checksum How to use checksums |
4a1801ac41fd5a11c1b0f0bd4ce6df6180169493ce6d455a35337f413ae3f736
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for arkeo 0.2.6
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.
