Archaeologist
See https://github.com/prathik-arun/archaeologist for full docs.
1 maintainer
Metadata
1 maintainer
Release files for archaeologist 0.9.3
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 | |
|---|---|---|---|---|
| archaeologist-0.9.3.tar.gz | 57.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| archaeologist-0.9.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 122.5 kB
Release files / archaeologist-0.9.3.tar.gz
| Download URL | archaeologist-0.9.3.tar.gz |
|---|---|
| Size | 57.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29711ec42bf1c8a11a5d892a6817c6e153650f1d7bc4382fba85f09f4eaaa33a
|
|
BLAKE2b-256 checksum How to use checksums |
068959a3f38a0d178fa39b09a312c10a4a713cf9702244333a291b242dae42f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / archaeologist-0.9.3-py3-none-any.whl
| Download URL | archaeologist-0.9.3-py3-none-any.whl |
|---|---|
| Size | 64.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eee7d2c00c279e0f288a785c96377ffba2eaf020afda9471b5585605f81ce065
|
|
BLAKE2b-256 checksum How to use checksums |
cc42b9b95482ab80bd54ca24abc2d7bd8347eddf71dced1f91c1ab7a9bcd6f08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for archaeologist 0.9.3
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.
