chromem-go has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test chromem-go?

On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.

Where is the evidence for chromem-go?

All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

chromem-go

Embeddable vector database for Go with Chroma-like interface and zero third-party dependencies. In-memory with optional persistence.

Not yet testedsource: GitHubGoMPL-2.0commit 0622e2f6bedd

Go, MPL-2.0 licensed. The project labels itself: chroma, chromadb, cosine similarity, embedded, embeddings, go, golang and in memory.

chromem-go has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict: Not yet tested
Argusic Score: not scored yet
recorded runs: 0
last tested: -
stars: 1,063
forks: 76
open issues: 17
watchers: 12
size: 0 MB
created: 2023-12-24
last push: 2026-09-06

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-08. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

chroma chromadb cosine-similarity embedded embeddings go golang in-memory llm llms nearest-neighbor rag retrieval-augmented-generation vector-database vector-search

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/chromem-go.svg)](https://argusic.com/subject/chromem-go)

Questions

Does chromem-go run?: chromem-go has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test chromem-go?: On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for chromem-go?: All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.