Chromadb Plugin
v2.0.0Integrates ChromaDB vector database with OpenClaw, enabling GPU-accelerated, zero-migration, multi-collection vector memory and hybrid search.
⭐ 0· 86·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (ChromaDB vector store for OpenClaw) align with the included Python plugin, migration script, tests, docs, and installer. The files implement a local/persistent ChromaDB client and optional cloud client (host/port/api_key) which is appropriate for a vector-store plugin. Minor marketing/instruction wording (e.g., “5-second one‑click install”) is optimistic compared to the actual install steps but not a security mismatch.
Instruction Scope
SKILL.md instructs running install.sh and migrate_lancedb.py and editing config.yaml — all consistent with installing a plugin and migrating data. The installer copies files into ~/.openclaw and creates a chromadb_config.yaml; the migration script modifies sys.path to include ~/.openclaw to import local OpenClaw modules. These actions affect user home config and rely on local filesystem access as expected for a plugin/migration tool.
Install Mechanism
There is no platform-level automated install spec, but an included install.sh is provided and is the documented installation path. The script runs pip3 install chromadb sentence-transformers pyyaml (PyPI packages) and copies files into ~/.openclaw/extensions — a moderate-risk but typical approach. No downloads from untrusted personal servers, URL shorteners, or IP-only hosts were found in the files.
Credentials
The skill declares no required env vars or primary credential. The code accepts optional host/port/api_key for cloud deployments and the docs list optional CHROMADB_* env vars — these are proportional and expected for a database connector. There are no hidden requests for unrelated credentials or secrets in the code.
Persistence & Privilege
always:false. The installer writes plugin files and a config file to the user's home (~/.openclaw), which is normal for an extension. The skill does not modify other skills or system-wide settings beyond adding its own extension files and config.
Assessment
This package appears coherent for integrating ChromaDB into OpenClaw, but follow these precautions before installing: 1) Run the installer inside a virtualenv, container, or test environment so pip installs don't affect global Python. 2) Back up any existing LanceDB data before running the migration script. 3) Inspect ~/.openclaw/config and ~/.openclaw/extensions after installation to confirm only expected files were written. 4) If you use a cloud ChromaDB endpoint, provide an API key only when needed and verify network traffic. 5) Run test_chromadb.py in an isolated environment to validate functionality before deploying to production.Like a lobster shell, security has layers — review code before you run it.
latestvk975xt0wd96exj9emqc60fm91d84cajq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.