inator3000
Part of inator3000 (GitHub). This name is reserved; the package is not published on PyPI yet.
Metadata
Release files for inator3000 0.0.0
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 | |
|---|---|---|---|---|
| inator3000-0.0.0.tar.gz | 982 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inator3000-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / inator3000-0.0.0.tar.gz
| Download URL | inator3000-0.0.0.tar.gz |
|---|---|
| Size | 982 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e5f5646e90685eb8268f9baf238de2cfa119a9303f0bdc3c6be2045d84ad8e6
|
|
BLAKE2b-256 checksum How to use checksums |
15e8fbc152b79c6b3f7473bf2e85729ab5652770ac141873613e493768c1b904
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / inator3000-0.0.0-py3-none-any.whl
| Download URL | inator3000-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36422c6d7f1339752eaac4ef03b0dc865fb42ab5ebe9377c230b57b2afdc40ae
|
|
BLAKE2b-256 checksum How to use checksums |
8f94b43b252b67544acc6ab7c7baed0a39ab483a3fde104bc38c1f1e61c26329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for inator3000 0.0.0
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.