1 maintainer
Metadata
1 maintainer
Release files for embedding-similarity 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 | |
|---|---|---|---|---|
| embedding_similarity-0.1.0.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embedding_similarity-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / embedding_similarity-0.1.0.tar.gz
| Download URL | embedding_similarity-0.1.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9014f5d18acbf5775e8d55255fb91fc67f1194e8b02e294c41386a1ac855b7b
|
|
BLAKE2b-256 checksum How to use checksums |
ece340facffdd51c3eaedb76bc237d79a50508220ea53cd9c1194da4236660f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / embedding_similarity-0.1.0-py3-none-any.whl
| Download URL | embedding_similarity-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6a284fa6c2c439ca0a41580e6dc302905bb34fcd177e2e29841e7a6ddd8d132
|
|
BLAKE2b-256 checksum How to use checksums |
5c2f5e57235b52184623dfd3a36004e66dea80179da66510834fe4c4322fbdbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for embedding-similarity 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.
