Is Chroma safe to use?

Chroma has an HVTrust score of 74.3/100 (Grade B), ranked #93 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Chroma?

Chroma scores 74.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 29.0k GitHub stars and is categorized under Memory & Knowledge.

Chroma

chroma-core/chroma

Search infrastructure for AI

Memory & Knowledge Rust Grade B Listed Apache-2.0

74.3/100

Rank #93 of 1204

Compare Chroma

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-07 · 2d ago

Recent change

Provider Added

Is Chroma safe? Chroma scores 74.3/100 (Grade B), ranked #93 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 100% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#7 FAISS — 75.6 (B) → #8 Weaviate — 75.0 (B) → #10 ReMe — 73.6 (B) → #11 GraphRAG — 72.8 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Cohere, Google Gemini

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Chroma View Memory & Knowledge Report missing data

88.3

Activity sub-score · out of 100

In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

29.0k

Forks

2.4k

Last Push

2026-08-07

2 days ago

Commits (4 wk)

Downloads (7d)

2,853,173

pypi

HN mentions (30d)

Open Issues

333

Rank Change

▼1

was #92

Analysis

HVTrust Dimensions vs Memory & Knowledge

74.3 / 100 · 100.0% confidence

Chroma Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.5 / 25

in line with avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.7

Maintenance60% last-push freshness · 40% commit activity

18.5 / 20

1.0 above avg 17.5

AdoptionLog-scaled stars · package downloads

19.3 / 20

5.2 above avg 14.1

Activity Inputs

88.3 / 100

StarsRepository reach

26.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

20.9 / 25

CommunityFork signal

15.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 9

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Chroma safe?

Chroma has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Chroma publish package provenance?

No published build provenance is currently detected for Chroma. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Chroma have an OpenSSF Scorecard?

Chroma has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Chroma actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Chroma use?

Chroma ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Chroma's commits signed?

100% of the last 100 commits to Chroma are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Chroma's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Cohere, Google Gemini

2026-06-26

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

Maintain Chroma?

For maintainers

HVTrust scores Chroma from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Cohere, Google Gemini

2026-06-26

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-20

Rank Moved

Rank rose 11 spots (#67 → #56)

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (58.3 → 68.2)

2026-05-28

Activity Score Changed

Activity score up 24pts (67 → 91)

2026-05-27

HVTrust Changed

HVTrust up 12.8pts (51.9 → 64.7)

2026-05-25

Newly Listed

First tracked at rank #55

GitHub → PyPI: chromadb

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/chroma.svg)](https://hvtracker.net/agents/chroma)
            
HTML:
            <a href="https://hvtracker.net/agents/chroma"><img src="https://hvtracker.net/badge/chroma.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON