Ahoy! Salutations
Metadata
Release files for neural-inquisitor 0.1.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 | |
|---|---|---|---|---|
| neural_inquisitor-0.1.0.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neural_inquisitor-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 kB
Release files / neural_inquisitor-0.1.0.tar.gz
| Download URL | neural_inquisitor-0.1.0.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e44e64f8f74f0a16c567cfe7d29bef4c71b10c9e995ba30ef53a43d2630c7885
|
|
BLAKE2b-256 checksum How to use checksums |
322d8756c4159d12a2daf6ce18eee233a84dc0464ac20bcc706961442ff42768
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / neural_inquisitor-0.1.0-py3-none-any.whl
| Download URL | neural_inquisitor-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f0b694b8bcd66beed00a36f1ca5534c19b0f9879dec8c7de08bcc711262e8a3
|
|
BLAKE2b-256 checksum How to use checksums |
6c35e023a3ae7810abf81b4dda53d6f83174927584fc99972f09a8020a3624c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for neural-inquisitor 0.1.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.