reserved for the Nemac project
1 maintainer
Metadata
1 maintainer
Release files for scrystone 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 | |
|---|---|---|---|---|
| scrystone-0.0.1.tar.gz | 459 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scrystone-0.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 1.5 kB
Release files / scrystone-0.0.1.tar.gz
| Download URL | scrystone-0.0.1.tar.gz |
|---|---|
| Size | 459 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee35d03fbf2026778311a641a73085458e31c6c45fb80ada6e048f24a975d820
|
|
BLAKE2b-256 checksum How to use checksums |
06197ed54e8800171dc4b77a95938c4401600612e4162a5b2f3de470f0a1b8d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / scrystone-0.0.1-py2.py3-none-any.whl
| Download URL | scrystone-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
015191b32d8f0dc4ae1b58739a8a7015a587f8d156208c2a8cff563235e536b4
|
|
BLAKE2b-256 checksum How to use checksums |
6ac899178623e56b773e01546848503cecb45cb83a563faf05c48389824b32b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for scrystone 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.
