2 maintainers
Metadata
2 maintainers
Release files for shennong 0.0.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 | |
|---|---|---|---|---|
| shennong-0.0.0.tar.gz | 733 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shennong-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / shennong-0.0.0.tar.gz
| Download URL | shennong-0.0.0.tar.gz |
|---|---|
| Size | 733 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32babbf92dca268fc11851e14490c62a8d5431eb0836692d89a036e88fbe7eeb
|
|
BLAKE2b-256 checksum How to use checksums |
1dbe814833873a4212db92870463cf2755bab4ae4af081340fb617b3cbcfc6c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / shennong-0.0.0-py3-none-any.whl
| Download URL | shennong-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3cbb4ed1b5cb9f1d608180c4bdadf52b3ea5308b2cc5377ae813f06b4fe679b
|
|
BLAKE2b-256 checksum How to use checksums |
f3864d4378e05c360cacda6e6ab279a8ea9a487fe54de44ee7c5ac670a646ff3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for shennong 0.0.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.
