Metadata
Release files for python-semantic-retrieval 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 | |
|---|---|---|---|---|
| python-semantic-retrieval-0.1.3.tar.gz | 34.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_semantic_retrieval-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.3 kB
Release files / python-semantic-retrieval-0.1.3.tar.gz
| Download URL | python-semantic-retrieval-0.1.3.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7551b6e75d45d99c3a44ae7d7a77b13312ee28fd7c646492ed3fa9c074a133a4
|
|
BLAKE2b-256 checksum How to use checksums |
95b091c4b303da18592f40dc9d282c200cdc88862587611d1de46225eb98652a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / python_semantic_retrieval-0.1.3-py3-none-any.whl
| Download URL | python_semantic_retrieval-0.1.3-py3-none-any.whl |
|---|---|
| Size | 53.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74cbe387f4807df80a01e80116c0ddc8224c425045701be767cb615328250089
|
|
BLAKE2b-256 checksum How to use checksums |
65c9144ef766a1cefa0dc440544da5ebc9983c6438ee20bdb5f57ab7007e1ff8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for python-semantic-retrieval 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.