2 maintainers
Metadata
2 maintainers
Release files for hypothesizing-machine 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 | |
|---|---|---|---|---|
| hypothesizing_machine-0.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hypothesizing_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / hypothesizing_machine-0.0.1.tar.gz
| Download URL | hypothesizing_machine-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e34ee2fe7b53f15cdd12e488662cc250e07224a56775e10b02089501509ff79a
|
|
BLAKE2b-256 checksum How to use checksums |
b57218d74dcf67f9a3171b9ce963f9e4a3b43ebbe4818b9fb216bf28b9cbb849
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / hypothesizing_machine-0.0.1-py3-none-any.whl
| Download URL | hypothesizing_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
890fc9e6c914adb249f3c51eace4bc406d9f135d2f0fa72985aca82b54e51dfd
|
|
BLAKE2b-256 checksum How to use checksums |
466f24885f8814078504ffa3759c20f3b880f08b4e1946019517474eca6f8d00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for hypothesizing-machine 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.
