The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for slickconf 0.1.16
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 | |
|---|---|---|---|---|
| slickconf-0.1.16.tar.gz | 30.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slickconf-0.1.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.6 kB
Release files / slickconf-0.1.16.tar.gz
| Download URL | slickconf-0.1.16.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
069071a3ae8c9f32502d58ac90b90602d95c02b22eeb378f9b0103b2ab701518
|
|
BLAKE2b-256 checksum How to use checksums |
93642709c0c1cb22806473cfae53f894b120c4e902107280bbbae98469d3cde3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.6
|
Release files / slickconf-0.1.16-py3-none-any.whl
| Download URL | slickconf-0.1.16-py3-none-any.whl |
|---|---|
| Size | 35.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f04f2f5f658865d3261642b66f3f25449684562a26c208fe9aa762edb810e6c
|
|
BLAKE2b-256 checksum How to use checksums |
c1ed575df9cde5105b387095c50cda2c7f4220a0e0bf100387a66246d7440a98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.6
|
Security for slickconf 0.1.16
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.
