updated 2026-08-09 19:31 UTC

LocalAI

mudler/LocalAI

LocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU requir

LLM Gateways & Infra Go Grade D Listed MIT
39.0/100
Rank #618 of 1204
Compare LocalAI

How does it stack up against its LLM Gateways & Infra neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-09 · 0d ago
Recent change
Rank +2

Is LocalAI safe? LocalAI scores 39.0/100 (Grade D), ranked #618 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 99% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in LLM Gateways & Infra

#9 Portkey AI Gateway — 57.5 (C) → #10 Chat Nio — 39.7 (D) → #12 claude-code-router — 25.2 (D) → #13 ClawRouter — 22.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 221 spots (#397 → #618)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 LocalAI View LLM Gateways & Infra Report missing data
95.0
Activity sub-score · out of 100
#11
In LLM Gateways & Infra

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

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed today

Activity & Reach

Stars
48.4k
Forks
4.3k
Last Push
2026-08-09
today
Commits (4 wk)
468
Downloads (7d)
—
HN mentions (30d)
675
Open Issues
92
Rank Change
=
was #618

Analysis

HVTrust Dimensions vs LLM Gateways & Infra

39.0 / 100 · 67.0% confidence

LocalAI LLM Gateways & Infra average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
5.1 below avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.6 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.7 above avg 17.3
AdoptionLog-scaled stars · package downloads
11.2 / 20
2.7 below avg 13.9

Activity Inputs

95.0 / 100
StarsRepository reach
28.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
99%
of last 100 commits verified

Is LocalAI safe?

Public trust evidence for LocalAI is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does LocalAI publish package provenance?
No published build provenance is currently detected for LocalAI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LocalAI have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for LocalAI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is LocalAI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does LocalAI use?
LocalAI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LocalAI's commits signed?
99% of the last 100 commits to LocalAI 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
high confidence
Implemented
LocalAI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency 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
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
How this surface has changed

Detected changes to LocalAI'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
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain LocalAI?

For maintainers

HVTrust scores LocalAI 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 9Surface 2Listed 1MCP 1Surface 1Surface 1
2026-08-08
Rank Moved
Rank dropped 221 spots (#397 → #618)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, OpenAI, Postgres
2026-07-29
Rank Moved
Rank dropped 11 spots (#381 → #392)
2026-07-15
Rank Moved
Rank dropped 25 spots (#352 → #377)
2026-07-14
Rank Moved
Rank dropped 20 spots (#332 → #352)
2026-07-13
Rank Moved
Rank dropped 36 spots (#296 → #332)
2026-06-24
Rank Moved
Rank dropped 35 spots (#264 → #299)
2026-06-23
Rank Moved
Rank dropped 22 spots (#242 → #264)
2026-06-22
Rank Moved
Rank dropped 10 spots (#232 → #242)
2026-06-21
Rank Moved
Rank dropped 15 spots (#217 → #232)
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-06-02
Newly Listed
First tracked at rank #178
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in LLM Gateways & Infra

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