This release is a pre-release and may not be stable for production use.
Metadata
Release files for dnsearch 0.1a1
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 | |
|---|---|---|---|---|
| dnsearch-0.1a1.tar.gz | 14.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dnsearch-0.1a1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 29.7 kB
Release files / dnsearch-0.1a1.tar.gz
| Download URL | dnsearch-0.1a1.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91dd29fe78260a93d73d5404bf03e10edf9967f4503f73d255ac89731aa54091
|
|
BLAKE2b-256 checksum How to use checksums |
4ace885832042bc9bb13c07a76ec6de24c93053121b017f00525afbcb5e417dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / dnsearch-0.1a1-py2.py3-none-any.whl
| Download URL | dnsearch-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f67218d9e7a07edfc57369317839fbccc94853980a80c3d3c611ce55d212f8d0
|
|
BLAKE2b-256 checksum How to use checksums |
42d1167c763c6dddb3b5128bea1f0b033f6e44994f8f6f8df5b5aaa687439293
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for dnsearch 0.1a1
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.