updated 2026-10-16 16:07 UTC

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 Apache-2.0

Is OpenExecutive safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 100%
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 65.2/100 (Grade B), ranked #499 of 1378 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 5.4/10; 100% of recent commits are signed; last pushed 2026-10-16. 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenExecutive and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/SenteLabsAI/OpenExecutive, Apache-2.0, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 0
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 3

  3. Published packages None

    No registry package. OpenExecutive is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-10-02 OSSF Scorecard: 5.4/10
  • 2026-09-30 License changed from NOASSERTION to Apache-2.0

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues OpenExecutive’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How OpenExecutive compares in Multi-Agent Systems

  1. #8 agent-swarm 65.9 +0.7
  2. #9 Ruflo 65.8 +0.6
  3. #10 OpenExecutive 65.2 this agent
  4. #11 TradingAgents 65.2 ±0
  5. #12 OpenBot 64.7 −0.5

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

Where the 65.2 comes from

HVTrust dimensions vs the Multi-Agent Systems average

65.2 / 100 · 100.0% confidence

OpenExecutive Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.8 / 25
3.1 above avg 8.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.9 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.8 above avg 13.2
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.2 below avg 10.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Grade Changed
Trust grade C → B
2026-10-03
Grade Changed
Trust grade B → C
2026-10-03
Rank Moved
Rank dropped 14 spots (#471 → #485)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
Compare with another agent Get email alerts for OpenExecutive View Multi-Agent Systems Report missing data
85.4
Activity sub-score · out of 100
#10
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 B 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-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
5.6k
Forks
604
Last Push
2026-10-16
today
Commits (4 wk)
448
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▲3
was #502

Analysis

Activity Inputs

85.4 / 100
StarsRepository reach
22.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.9 / 20

Common questions about OpenExecutive

OpenExecutive has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
OpenExecutive has an OpenSSF Scorecard score of 5.4/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 OpenExecutive actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenExecutive use?
OpenExecutive ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenExecutive's commits signed?
100% 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
Grade 3Rank 2Listed 1License 1HVTrust 1Scorecard 1
2026-10-15
Grade Changed
Trust grade C → B
2026-10-03
Grade Changed
Trust grade B → C
2026-10-03
Rank Moved
Rank dropped 14 spots (#471 → #485)
2026-10-02
Scorecard Added
OSSF Scorecard: 5.4/10
2026-10-02
Grade Changed
Trust grade D → B
2026-10-02
Rank Moved
Rank rose 850 spots (#1321 → #471)
2026-10-02
HVTrust Changed
HVTrust up 38.1pts (27.1 → 65.2)
2026-09-30
License Changed
License changed from NOASSERTION to Apache-2.0
2026-09-29
Newly Listed
First tracked at rank #1316
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.2 Grade B
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON