Is RoboOS safe to use?

RoboOS has an HVTrust score of 33.7/100 (Grade D), ranked #682 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for RoboOS?

RoboOS scores 33.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 608 GitHub stars and is categorized under Robotics & Embodied.

RoboOS

FlagOpen/RoboOS

🤖 RoboOS: A Universal Embodied Operating System for Cross-Embodied and Multi-Robot Collaboration

Robotics & Embodied Python Grade D Listed Apache-2.0

33.7/100

Rank #682 of 1204

Compare RoboOS

How does it stack up against its Robotics & Embodied 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

2025-12-18 · 234d ago

Recent change

Rank

Is RoboOS safe? RoboOS scores 33.7/100 (Grade D), ranked #682 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; OSSF Scorecard rates its supply-chain practices 1.8/10; 100% of recent commits are signed; last pushed 2025-12-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Robotics & Embodied

#1 LeRobot — 89.7 (A) → #2 Habitat-Lab — 47.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 264 spots (#417 → #681)

2026-07-29

Scorecard Added

OSSF Scorecard: 1.8/10

2026-07-29

Rank Moved

Rank rose 33 spots (#441 → #408)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.8/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.

Refresh maintenance signals The repo was last pushed 234 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with LeRobot Get email alerts for RoboOS View Robotics & Embodied Report missing data

25.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 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 →

Activity & Reach

Stars

608

Forks

Last Push

2025-12-18

234 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #681

Analysis

HVTrust Dimensions

33.7 / 100 · 100.0% confidence

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

7.3 / 25

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

Transparency50% declared license · 50% OSSF Scorecard

10.0 / 17

Maintenance60% last-push freshness · 40% commit activity

0.0 / 20

AdoptionLog-scaled stars · package downloads

6.7 / 20

Activity Inputs

25.8 / 100

StarsRepository reach

16.7 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.8 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 2

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is RoboOS safe?

Public trust evidence for RoboOS 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 RoboOS publish package provenance?

No published build provenance is currently detected for RoboOS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does RoboOS have an OpenSSF Scorecard?

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

Stale. The repository has not been pushed to in 234 days. Consider whether the project is still being maintained.

What license does RoboOS use?

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

Are RoboOS's commits signed?

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

RoboOS vs LeRobot → RoboOS vs Habitat-Lab →

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

high confidence

2 detected

Public provider/service dependencies detected.

OpenAI
Redis

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

code
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 RoboOS?

For maintainers

HVTrust scores RoboOS 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-08

Rank Moved

Rank dropped 264 spots (#417 → #681)

2026-07-29

Scorecard Added

OSSF Scorecard: 1.8/10

2026-07-29

Rank Moved

Rank rose 33 spots (#441 → #408)

2026-07-29

HVTrust Changed

HVTrust up 19.3pts (14.4 → 33.7)

2026-07-28

Newly Listed

First tracked at rank #441

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Robotics & Embodied

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