Is OpenExecutive safe to use?

OpenExecutive has an HVTrust score of 26.9/100 (Grade D), ranked #1314 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenExecutive?

OpenExecutive scores 26.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 5.4k GitHub stars and is categorized under Multi-Agent Systems.

OpenExecutive

Repository Website

AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).

Multi-Agent Systems Python Listed NOASSERTION

Is OpenExecutive safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result

Provenance None

Signed commits 90%

Last push today

Compare OpenExecutive

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Suggest a correction

In detail: OpenExecutive scores 26.9/100 (Grade D), ranked #1314 of 1343 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; 90% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenExecutive 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 to 9.0no OSSF Scorecard result yet +45.3 → 72.2 B · #3 of 41

Already done? Suggest a correction Add the trust badge

How OpenExecutive compares in Multi-Agent Systems

Bars show each HVTrust score; the tick marks OpenExecutive’s 26.9.

Where the 26.9 comes from

HVTrust dimensions vs the Multi-Agent Systems average

26.9 / 100 · 50.0% confidence

OpenExecutive Multi-Agent Systems average (41 agents)

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

4.5 / 25

3.5 below avg 8.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.4 below avg 11.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.2 above avg 12.8

AdoptionLog-scaled stars · package downloads

9.0 / 20

1.1 below avg 10.1

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-09-29

Newly Listed

First tracked at rank #1314

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 OpenExecutive View Multi-Agent Systems Report missing data

85.2

Activity sub-score · out of 100

#38

In Multi-Agent Systems

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 →

Activity & Reach

Stars

5.4k

Forks

569

Last Push

2026-09-29

today

Commits (4 wk)

360

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

85.2 / 100

StarsRepository reach

22.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

90%

of last 100 commits verified

Common questions about OpenExecutive

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

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

Does OpenExecutive have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for OpenExecutive. 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 OpenExecutive actively maintained?

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

What license does OpenExecutive use?

OpenExecutive ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OpenExecutive's commits signed?

90% of the last 100 commits to OpenExecutive 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

OpenExecutive appears to expose MCP server capabilities.

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

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

Maintain OpenExecutive?

For maintainers

HVTrust scores OpenExecutive 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-09-29

Newly Listed

First tracked at rank #1314

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Multi-Agent Systems

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