Trust and health report
chroma - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 3w · GitHub synced 3w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 0d ago · last release 3mo · 3 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 546206616
- Not a fork
- Verified publisher: organization account
- Computed 3w
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 8
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/chroma-core-chroma/trust.
Common questions
- Is chroma maintained?
- GraphCanon rates chroma "Very active" (96% maintenance signal from public GitHub metadata, computed 3w). Last push was 0 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is chroma safe to use?
- Last scanned 1mo (deps profile). Status: 8 low - 8 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify chroma as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is chroma a fork?
- No. chroma is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does chroma have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 8 low - 8 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the chroma trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 3w (methodology github_public_v1).
- What does GraphCanon never claim about chroma?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for chroma. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for chroma?
- Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.