Is LeRobot safe to use?

LeRobot has an HVTrust score of 89.7/100 (Grade A), ranked #13 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LeRobot?

LeRobot scores 89.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 26.5k GitHub stars and is categorized under Robotics & Embodied.

LeRobot

huggingface/lerobot

🤗 LeRobot: Making AI for Robotics more accessible with end-to-end learning

Robotics & Embodied Python Grade A Listed Apache-2.0

89.7/100

Rank #13 of 1204

Compare LeRobot

How does it stack up against its Robotics & Embodied neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Tool Surface Changed +1

Is LeRobot safe? LeRobot scores 89.7/100 (Grade A), ranked #13 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% 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 Robotics & Embodied

#2 Habitat-Lab — 47.6 (D) → #3 RoboOS — 33.7 (D) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.

Compare with Habitat-Lab Get email alerts for LeRobot View Robotics & Embodied Report missing data

93.8

Activity sub-score · out of 100

In Robotics & Embodied

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 →

Activity & Reach

Stars

26.5k

Forks

5.4k

Last Push

2026-08-09

today

Commits (4 wk)

156

Downloads (7d)

52,836

pypi

HN mentions (30d)

Open Issues

330

Rank Change

was #13

Analysis

HVTrust Dimensions

89.7 / 100 · 100.0% confidence

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

20.7 / 25

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

AdoptionLog-scaled stars · package downloads

16.9 / 20

Activity Inputs

93.8 / 100

StarsRepository reach

26.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

17.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 6

Security-Policy 10

Signed-Releases 0

Token-Permissions 8

Vulnerabilities 1

Is LeRobot safe?

Public supply-chain signals for LeRobot are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but LeRobot carries less obvious unverified-evidence risk than projects with thin signals.

Does LeRobot publish package provenance?

Yes. LeRobot's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does LeRobot have an OpenSSF Scorecard?

LeRobot has an OpenSSF Scorecard score of 6.6/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 LeRobot actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does LeRobot use?

LeRobot ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are LeRobot's commits signed?

100% of the last 100 commits to LeRobot 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 LeRobot head-to-head

LeRobot vs Habitat-Lab → LeRobot vs RoboOS →

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

OpenAI

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

low confidence

Unknown

Package source metadata is missing or inconclusive

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 LeRobot'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: Postgres

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-15

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-06-13

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

Maintain LeRobot?

For maintainers

HVTrust scores LeRobot 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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

2026-06-16

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-15

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-06-13

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (78.9 → 88.9)

2026-05-28

Activity Score Changed

Activity score up 21pts (68 → 90)

2026-05-27

Scorecard Added

OSSF Scorecard: 6.7/10

2026-05-27

HVTrust Changed

HVTrust up 28.5pts (43.8 → 72.3)

2026-05-25

Newly Listed

First tracked at rank #47

GitHub → PyPI: lerobot

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/lerobot.svg)](https://hvtracker.net/agents/lerobot)
            
HTML:
            <a href="https://hvtracker.net/agents/lerobot"><img src="https://hvtracker.net/badge/lerobot.svg" alt="HVTrust"></a>

Other agents in Robotics & Embodied

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