The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for seghouse 0.18.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 | |
|---|---|---|---|---|
| seghouse-0.18.0.tar.gz | 10.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seghouse-0.18.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.5 kB
Release files / seghouse-0.18.0.tar.gz
| Download URL | seghouse-0.18.0.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34ccdbccb0a02fe9005d345b7f1aa87d62d13b32e23df4ef8276566303152fdc
|
|
BLAKE2b-256 checksum How to use checksums |
2455e69a55eb371fa0f1346071d817c99a47dbd42547a058743cc36130bc9241
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.9.0 Darwin/18.7.0
|
Release files / seghouse-0.18.0-py3-none-any.whl
| Download URL | seghouse-0.18.0-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92e7e7094b215f91b4eb87cfb906970b2951ef989c91daf59faad9b679dad4c4
|
|
BLAKE2b-256 checksum How to use checksums |
e234508727b87dc9c295dfff892749fb22a4691f6c2665b5b63097e2a9278172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.9.0 Darwin/18.7.0
|
Security for seghouse 0.18.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.
