The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lingergrn 1.111
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 | |
|---|---|---|---|---|
| lingergrn-1.111.tar.gz | 32.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lingergrn-1.111-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.5 kB
Release files / lingergrn-1.111.tar.gz
| Download URL | lingergrn-1.111.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9efad53d498fcce87cfb5b0820aaa5c0383364af0f768436c43f98bde4a0ad85
|
|
BLAKE2b-256 checksum How to use checksums |
bf3209c9c159b9384f828a3fecd504d77a2b0f20ef5b019afa66ae0967c555ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / lingergrn-1.111-py3-none-any.whl
| Download URL | lingergrn-1.111-py3-none-any.whl |
|---|---|
| Size | 37.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df3ba026fa44d054d75e75537401448cf71a9f5b6f8815f99d933b55dd0bceb3
|
|
BLAKE2b-256 checksum How to use checksums |
58faca524134c5599bb09320c13d9a1a8a8e21938a999d55041a80440b581236
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for lingergrn 1.111
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.
