The author of this package has not provided a project description
4 maintainers
Metadata
4 maintainers
Release files for conftool 6.1.0
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 | |
|---|---|---|---|---|
| conftool-6.1.0.tar.gz | 88.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conftool-6.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 190.3 kB
Release files / conftool-6.1.0.tar.gz
| Download URL | conftool-6.1.0.tar.gz |
|---|---|
| Size | 88.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3175a984f9bd0804a04a2407a0bc2b6aeb8cb32c0baedbcd3b234b9e018267c
|
|
BLAKE2b-256 checksum How to use checksums |
9e81d92d737e9cdbf423a45be6df454d96b70c2738f7ae0b6a35dd2ab495d8bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / conftool-6.1.0-py3-none-any.whl
| Download URL | conftool-6.1.0-py3-none-any.whl |
|---|---|
| Size | 101.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
811b9784c12a4bfec442b1265ad6573ef6c2eae531ace1659d5d61da9de54fbd
|
|
BLAKE2b-256 checksum How to use checksums |
ee0a759350c60fca8f2fe25156aea4b181e4ae24867360b4a5192876bfdf3822
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for conftool 6.1.0
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.
