2 maintainers
Metadata
2 maintainers
Release files for understanding-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 | |
|---|---|---|---|---|
| understanding_machine-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| understanding_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / understanding_machine-0.0.1.tar.gz
| Download URL | understanding_machine-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ffc44ecc181830858be7b51454e71a1e514a2f5937ddc4394ded2d4ee1098d8
|
|
BLAKE2b-256 checksum How to use checksums |
83aaa356e1bae612977dbab13f47eda4363ccf26bc66028acff2b60d8475e4ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / understanding_machine-0.0.1-py3-none-any.whl
| Download URL | understanding_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7c077b471036f9395c1330a88c0815d77f54080686e33dcb9fceabf70407f01
|
|
BLAKE2b-256 checksum How to use checksums |
858fc89c4fc931b7a50d25d31eeb55365b1190852cdacc45c5a5e26461f148dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for understanding-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.
