updated 2026-10-09 20:07 UTC

Chroma

Repository Website

Search infrastructure for AI

Memory & Knowledge Rust Listed Apache-2.0

CRITICAL4 unfixed advisories in the release you'd install

ChromaDB has a code injection vulnerability. It affects chromadb 1.5.9, the latest published release.

GHSA-36p7-vc44-83pf · CVE-2026-45833 · published 2026-06-12 · all 4

Is Chroma safe? Promising trust profile, but some evidence still deserves review. 4 published advisories affect its latest release.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 100%
Last push today
Advisories 4, worst critical
Compare Chroma

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

Pick any agent to compare →
Suggest a correction

In detail: Chroma scores 64.9/100 (Grade C), ranked #502 of 1371 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; 4 published advisories affect its latest release (chromadb); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Known advisories

Published advisories (from OSV) that affect the release you'd install today: chromadb 1.5.9. An unfixed critical advisory caps the HVTrust score at 64.9 (Grade C) and a high one at 79.9 (Grade B), until a fixed release ships; moderate, low and unrated ones are shown, not scored. Checked 2026-10-09.

  • CRITICAL ChromaDB has a code injection vulnerability GHSA-36p7-vc44-83pf · CVE-2026-45833 · chromadb 1.5.9 · published 2026-06-12
  • CRITICAL ChromaDB Python project has a pre-authentication code injection vulnerability GHSA-f4j7-r4q5-qw2c · CVE-2026-45829 · chromadb 1.5.9 · published 2026-05-18
  • HIGH ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection GHSA-2wm9-hf6c-p5cr · CVE-2026-45830 · chromadb 1.5.9 · published 2026-06-12
  • HIGH ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to GHSA-xph7-9rjv-w5fr · CVE-2026-45831 · chromadb 1.5.9 · published 2026-06-12

How Chroma could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Chroma and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/chroma-core/chroma, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    • PyPI chromadb Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today 4 advisories

    Latest release checked: chromadb 1.5.9. 4 published advisories affect it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Chroma.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Chroma’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Chroma compares in Memory & Knowledge

  1. #29 IWE 65.5 +0.6
  2. #30 Beads 65.0 +0.1
  3. #31 Chroma 64.9 this agent
  4. #32 Zvec 63.6 −1.3
  5. #33 PipesHub 62.0 −2.9

Bars show each HVTrust score; the tick marks Chroma’s 64.9.

Where the 64.9 comes from

HVTrust dimensions vs the Memory & Knowledge average

64.9 / 100 · 100.0% confidence

Chroma Memory & Knowledge average (49 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.5 / 25
1.0 below avg 11.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
0.5 below avg 12.7
Maintenance60% last-push freshness · 40% commit activity
18.6 / 20
1.2 above avg 17.4
AdoptionLog-scaled stars · package downloads
19.0 / 20
5.8 above avg 13.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 152 spots (#98 → #250)
2026-09-21
Rank Moved
Rank rose 162 spots (#260 → #98)
2026-09-14
Rank Moved
Rank rose 10 spots (#258 → #248)
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
#31
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 C 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 →

Signals refreshed 2026-10-09 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
29.5k
Forks
2.6k
Last Push
2026-10-09
today
Commits (4 wk)
45
Downloads (7d)
1,691,401
pypi
HN mentions (30d)
8
Open Issues
356
Rank Change
▼6
was #496

Analysis

Activity Inputs

88.3 / 100
StarsRepository reach
26.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
20.7 / 25
CommunityFork signal
15.8 / 20

Common questions about Chroma

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 1 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

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
Rank 8
2026-09-23
Rank Moved
Rank dropped 152 spots (#98 → #250)
2026-09-21
Rank Moved
Rank rose 162 spots (#260 → #98)
2026-09-14
Rank Moved
Rank rose 10 spots (#258 → #248)
2026-09-13
Rank Moved
Rank dropped 11 spots (#247 → #258)
2026-09-07
Rank Moved
Rank dropped 22 spots (#218 → #240)
2026-09-05
Rank Moved
Rank dropped 55 spots (#163 → #218)
2026-08-31
Rank Moved
Rank dropped 21 spots (#128 → #149)
2026-08-26
Rank Moved
Rank dropped 13 spots (#107 → #120)
GitHub → Website → PyPI: chromadb

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.9 Grade C
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.4 · Raw JSON