1 maintainer
Metadata
1 maintainer
Release files for pickledsocks-siiverfish 0.0.1
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 | |
|---|---|---|---|---|
| pickledsocks_siiverfish-0.0.1.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pickledsocks_siiverfish-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / pickledsocks_siiverfish-0.0.1.tar.gz
| Download URL | pickledsocks_siiverfish-0.0.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09b8c13d159a96a12c05f433f96cd56c1e63604a293e5bed7e647a3a1ecf7d2d
|
|
BLAKE2b-256 checksum How to use checksums |
4dde6d9c359443c1ccd4b746b04e7cca43779f5cb5d00437206f8ac2382af933
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.2
|
Release files / pickledsocks_siiverfish-0.0.1-py3-none-any.whl
| Download URL | pickledsocks_siiverfish-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54e8cd5a457725b71ad6e072c616854a833213a525dd1fdbd416a6e9f513b17c
|
|
BLAKE2b-256 checksum How to use checksums |
2e14577a9781553c6feecaaee81fc3d49d641a8465f99bc655f6162b408bd250
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.2
|
Security for pickledsocks-siiverfish 0.0.1
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.
