2 maintainers
Metadata
2 maintainers
Release files for evaluating-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 | |
|---|---|---|---|---|
| evaluating_machine-0.0.1.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evaluating_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.7 kB
Release files / evaluating_machine-0.0.1.tar.gz
| Download URL | evaluating_machine-0.0.1.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28ab58b358504ad117caf7aa974491f8bc047e80a0e2761e81a128a5bd930c96
|
|
BLAKE2b-256 checksum How to use checksums |
a6d75b7155bd1406285b1bacf272aa7f8d2f3579cd552bd8531565b44e50a782
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / evaluating_machine-0.0.1-py3-none-any.whl
| Download URL | evaluating_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b19f8fc5bf1d08c3baf33f1545af8733ff698b0a17f398376126a9adf682bd1
|
|
BLAKE2b-256 checksum How to use checksums |
ae5bfeec3a7fb489f769646dab187cc65e341fab6a15bae1d6c231dcef1fc811
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for evaluating-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.
