OpenShell

OpenShell is the safe, private runtime for autonomous AI agents.

Sandboxes & Runtimes Rust Grade D Listed Apache-2.0
Compare → Suggest correction
Listing state
Listed
HVTrust
19.3/100 · Grade D
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-15 · 0d ago
Recent change
New

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

Quick Trust Read

Verdict
Thin or incomplete trust evidence. Review carefully before production use.
19.3/100 · Grade D
Strongest Signal
Maintenance
20.0/20
Weakest Signal
Safety / Integrity
5.0/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-14
Newly Listed
First tracked at rank #415
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.
87.4
Activity Score · out of 100
19.3
HVTrust Score · out of 100
#415
Global Rank · of 417
#7

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-07-15 01:00 UTC · Repo last pushed today

Rank Trend

2026-07-14 2026-07-15

Activity & Reach

Stars
7.7k
Forks
1.1k
Last Push
2026-07-15
today
Commits (4 wk)
115
Downloads (7d)
HN mentions (30d)
Open Issues
247
Rank Change
=
was #415

Analysis

HVTrust Dimensions

19.3 / 100 · 40.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
Adoption60% stars · 40% downloads, log-scaled
9.3 / 20

Activity Inputs

87.4 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.1 / 20

Supply Chain Trust

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

Is OpenShell safe?

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

Ranked neighbours in Sandboxes & Runtimes

AI agent 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.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration 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

Maintain OpenShell?

HVTrust scores OpenShell 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

Listed 1
2026-07-14
Newly Listed
First tracked at rank #415

Embed Badge Badge guide for maintainers →

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

Other agents in Sandboxes & Runtimes

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