Is LibreChat safe to use?

LibreChat has an HVTrust score of 72.0/100 (Grade B), ranked #304 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LibreChat?

LibreChat scores 72.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 45.4k GitHub stars and is categorized under UI & App Builders.

LibreChat

Repository

Website

Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1, GPT-5, Mistral, OpenRouter, Vertex AI, Gemini, Artifacts, AI model switching, message search, Code Interpreter, langchain, DALL-E-3, OpenAPI Actions, Functions, Secure Multi-User…

UI & App Builders TypeScript Listed MIT

Is LibreChat safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.7 / 10

Provenance None

Signed commits 81%

Last push today

Compare LibreChat

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Suggest a correction

In detail: LibreChat scores 72.0/100 (Grade B), ranked #304 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.7/10; 81% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How LibreChat 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.

Raise the OSSF Scorecard from 4.7 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +8.9 → 80.9 A · #4 of 18
Sign every commit81% signed today +1.0 → 73.0 B · #6 of 18

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Signed

github.com/LibreChat-AI/LibreChat, MIT, last pushed 2026-10-09. 81% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

Distributed as the container image librechat/librechat; HVTracker doesn't check that registry's source link yet.

Changes to this chain

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

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 LibreChat’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 LibreChat compares in UI & App Builders

Bars show each HVTrust score; the tick marks LibreChat’s 72.0.

Where the 72.0 comes from

HVTrust dimensions vs the UI & App Builders average

72.0 / 100 · 100.0% confidence

LibreChat UI & App Builders average (18 agents)

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

9.9 / 25

0.7 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.0 below avg 12.8

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

0.9 above avg 11.6

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.7 above avg 14.3

AdoptionLog-scaled stars · package downloads

18.9 / 20

7.0 above avg 11.9

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-08

Rank Moved

Rank dropped 30 spots (#272 → #302)

2026-09-27

Rank Moved

Rank dropped 16 spots (#250 → #266)

2026-09-23

Rank Moved

Rank dropped 156 spots (#102 → #258)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/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 Neo Get email alerts for LibreChat View UI & App Builders Report missing data

96.4

Activity sub-score · out of 100

In UI & App Builders

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 →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

45.4k

Forks

9.3k

Last Push

2026-10-09

today

Commits (4 wk)

610

Downloads (7d)

576,289

docker

HN mentions (30d)

Open Issues

423

Rank Change

▼2

was #302

Analysis

Activity Inputs

96.4 / 100

StarsRepository reach

27.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

18.5 / 20

Common questions about LibreChat

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 4.7/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?

81% 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

LibreChat vs Neo → LibreChat vs OpenUI → LibreChat vs Open WebUI →

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-08

Rank Moved

Rank dropped 30 spots (#272 → #302)

2026-09-27

Rank Moved

Rank dropped 16 spots (#250 → #266)

2026-09-23

Rank Moved

Rank dropped 156 spots (#102 → #258)

2026-09-21

Rank Moved

Rank rose 160 spots (#262 → #102)

2026-09-07

Rank Moved

Rank dropped 43 spots (#202 → #245)

2026-09-05

Rank Moved

Rank dropped 49 spots (#155 → #204)

2026-08-31

Rank Moved

Rank dropped 17 spots (#125 → #142)

2026-08-26

Rank Moved

Rank dropped 13 spots (#101 → #114)

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)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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.4 · Raw JSON

LibreChat

How LibreChat could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How LibreChat compares in UI & App Builders

Where the 72.0 comes from

HVTrust dimensions vs the UI & App Builders average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about LibreChat

Compare LibreChat head-to-head

AI agent surface

Maintain LibreChat?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in UI & App Builders