Python is trickier because of the lack of strong typing support by default in Python. So we're left with projects using strict mypy or with very extensive test suites for validation.
It's possible, just probably not the next language to tackle. If you'd like Python support though, you can upvote this github issue: https://github.com/xeol-io/bumpgen/issues/61
We cataloged more than 30,000+ deprecated packages from the major package registries and made it searchable.
Details:
- Top 10,000 most used npm packages
- Top 10,000 most used Maven packages. We consider a package deprecated if the source repository is archived, and a version has not been pushed after archive.
- All NuGet packages ever marked as deprecated on the registry
- In the case that a vendor has announced EOL/deprecation, like Vue or Bootstrap, we prefer that data over any we source directly from the registry.
How do you deal with data persistence for storing the documents/vectorDB inside a Nitro Enclave? I would assume that you as the SaaS vendor are unable to decrypt the sensitive documents inside the enclave or see a users chat history?
Good question! Uploaded documents get converted to embeddings within the Nitro Enclave (NE), and then the embeddings are encrypted with a key that only the NE has access to.
When the search endpoint is called the encrypted embeddings are pulled into the NE and decrypted. They are then loaded into a vector db in-memory and the search is executed all within the NE. This adds some latency but it’s more secure because embeddings are only accessible to the enclave.
In the case of chat history it is never stored by the API. The developer can develop their own client side. With CapeChat we keep chat history local on the device.
It's possible, just probably not the next language to tackle. If you'd like Python support though, you can upvote this github issue: https://github.com/xeol-io/bumpgen/issues/61