SvectorDB Client
For more information on SvectorDB, visit the website.
Metadata
Release files for svectordb 0.0.9
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 | |
|---|---|---|---|---|
| svectordb-0.0.9.tar.gz | 57.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| svectordb-0.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 133.2 kB
Release files / svectordb-0.0.9.tar.gz
| Download URL | svectordb-0.0.9.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90e234b494c58f4ddfea6d5d2928413bc46eb76929d8740d656bffc875781628
|
|
BLAKE2b-256 checksum How to use checksums |
ee9c70c01318eed5d7ed2c2b0e31881d9b99a7c86100a9bac5fcf9a3ec9df752
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Release files / svectordb-0.0.9-py3-none-any.whl
| Download URL | svectordb-0.0.9-py3-none-any.whl |
|---|---|
| Size | 75.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a72f0ae89b5aff86909d6bcf52c02dc4156e0d5fbf76aba1604f7b50520a2845
|
|
BLAKE2b-256 checksum How to use checksums |
5c6a9cd14107c4b844ed2cb2404bdaa2fc8715bef095db6aacebaa5cc3e80c45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Security for svectordb 0.0.9
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.