Metadata
Release files for sherlock-hollms 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 | |
|---|---|---|---|---|
| sherlock_hollms-0.0.1.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sherlock_hollms-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 kB
Release files / sherlock_hollms-0.0.1.tar.gz
| Download URL | sherlock_hollms-0.0.1.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33c5e492390cf1cb6a49b658ac9107e67eb0f51c59ea7078adfd51542cbeebbb
|
|
BLAKE2b-256 checksum How to use checksums |
faae054e6d3ce3b6cc0f5e121021dc6492531e7c6d94a36bde5de1b78268c5ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / sherlock_hollms-0.0.1-py3-none-any.whl
| Download URL | sherlock_hollms-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f85a69780ee14b01a5e6dbfe7713998dbe504ebb08f28dd30be94928aab62881
|
|
BLAKE2b-256 checksum How to use checksums |
b9817d552f23c919cf2342af99a8a1ffefa2d5c77b2dac4879d33fc21f91dc5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for sherlock-hollms 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.