2 maintainers
Metadata
2 maintainers
Release files for inventing-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 | |
|---|---|---|---|---|
| inventing_machine-0.0.1.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inventing_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / inventing_machine-0.0.1.tar.gz
| Download URL | inventing_machine-0.0.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e0b86d3041a5f817c2aea95b8d9975c80b02d85a26e6fc8e3ea77c8a780a51a
|
|
BLAKE2b-256 checksum How to use checksums |
32515fae99a8d5f51968353d39770bf5f0e9d16f23d077a4c2819f8936a8fba7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / inventing_machine-0.0.1-py3-none-any.whl
| Download URL | inventing_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e87442157816c36cf9ae3f30d27ae01487868862836110ecb34512946ca6fbda
|
|
BLAKE2b-256 checksum How to use checksums |
fc2128da8be74c7a7f8bff4762946dfd9ff59ead394f59e1ecc66d84f08034a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for inventing-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.
