The author of this package has not provided a project description
Metadata
Release files for logprobs-parser 0.1.3
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 | |
|---|---|---|---|---|
| logprobs_parser-0.1.3.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| logprobs_parser-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.7 kB
Release files / logprobs_parser-0.1.3.tar.gz
| Download URL | logprobs_parser-0.1.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
413b680f7e29ff2484e04ad91741159c294567e54e6c0115f05ea54ae9d2b04c
|
|
BLAKE2b-256 checksum How to use checksums |
85532950bc0fb665ad8e8ae4e71667a3f8a5daea242f33265f6a30ff99ed21bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Release files / logprobs_parser-0.1.3-py3-none-any.whl
| Download URL | logprobs_parser-0.1.3-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d987fee4e33000d0ef1689dd28b3b01a07ce1bd8cc8ade3eecd09863f58365ee
|
|
BLAKE2b-256 checksum How to use checksums |
b5a463268a69e1a2891aa38e902ac4b92670ae547d7d02b1abe28222da3879cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Security for logprobs-parser 0.1.3
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.