LibreChat

Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1,

UI & App Builders TypeScript Grade B Listed MIT
74.7/100
Rank #98 of 1308
Compare LibreChat

How does it stack up against its UI & App Builders 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-19 · 0d ago
Recent change
Rank +1

Is LibreChat safe? LibreChat scores 74.7/100 (Grade B), ranked #98 of 1308 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 5.9/10; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 10 spots (#88 → #98)
2026-08-12
Rank Moved
Rank rose 10 spots (#98 → #88)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/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.
96.1
Activity sub-score · out of 100
#5

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 →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
42.2k
Forks
8.7k
Last Push
2026-08-19
today
Commits (4 wk)
318
Downloads (7d)
181,893
docker
HN mentions (30d)
0
Open Issues
364
Rank Change
▼5
was #93

Analysis

HVTrust Dimensions vs UI & App Builders

74.7 / 100 · 100.0% confidence

LibreChat UI & App Builders average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.4 / 25
2.3 above avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
1.7 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.0 above avg 16.0
AdoptionLog-scaled stars · package downloads
18.1 / 20
5.7 above avg 12.4

Activity Inputs

96.1 / 100
StarsRepository reach
27.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.9 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 3
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is LibreChat safe?

LibreChat 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 LibreChat publish package provenance?
No published build provenance is currently detected for LibreChat. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LibreChat have an OpenSSF Scorecard?
LibreChat has an OpenSSF Scorecard score of 5.9/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 LibreChat actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does LibreChat use?
LibreChat ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LibreChat's commits signed?
100% of the last 100 commits to LibreChat 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.

Compare LibreChat head-to-head

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
high confidence
Implemented
LibreChat appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain LibreChat?

For maintainers

HVTrust scores LibreChat 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.

Reputation Timeline

Signal history
Rank 4HVTrust 3Listed 1Grade 1Scorecard 1Score 1
2026-08-13
Rank Moved
Rank dropped 10 spots (#88 → #98)
2026-08-12
Rank Moved
Rank rose 10 spots (#98 → #88)
2026-07-13
Rank Moved
Rank dropped 10 spots (#74 → #84)
2026-06-02
Rank Moved
Rank rose 27 spots (#69 → #42)
2026-06-02
HVTrust Changed
HVTrust up 7.0pts (66.9 → 73.9)
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (57.3 → 67.3)
2026-05-28
Activity Score Changed
Activity score up 25pts (70 → 96)
2026-05-27
Scorecard Added
OSSF Scorecard: 5.7/10
2026-05-27
Grade Changed
Trust grade D → C
2026-05-27
HVTrust Changed
HVTrust up 30.2pts (27.0 → 57.2)
2026-05-25
Newly Listed
First tracked at rank #36

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.7 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/librechat.svg)](https://hvtracker.net/agents/librechat)
HTML:
<a href="https://hvtracker.net/agents/librechat"><img src="https://hvtracker.net/badge/librechat.svg" alt="HVTrust"></a>

Other agents in UI & App Builders

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