2 maintainers
Metadata
2 maintainers
Release files for inquiring-machine 0.0.2
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 | |
|---|---|---|---|---|
| inquiring_machine-0.0.2.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inquiring_machine-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / inquiring_machine-0.0.2.tar.gz
| Download URL | inquiring_machine-0.0.2.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5603b568161bd4a0fbe5e7c2a8cbd6140cf3e4a27099a39f6c3eb00d23e009e
|
|
BLAKE2b-256 checksum How to use checksums |
1486a0c80ff387382dfb8e78d62fc9814223a78f9d9c07d6d5f4b424086ac82d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.20
|
Release files / inquiring_machine-0.0.2-py3-none-any.whl
| Download URL | inquiring_machine-0.0.2-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c18d50a2d5b0c0dc5fa005aa480072dc18bae064ab57aac47b1544eda944fa5
|
|
BLAKE2b-256 checksum How to use checksums |
153f6d2a80b0f4f1a99477d88436d0c44a138d6f7e570991a6c919aece9d9b08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.20
|
Security for inquiring-machine 0.0.2
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.
