updated 2026-10-03 16:08 UTC

Hexis

Repository Website

Centrally manage AI-agent skills, tools, context, permissions, and identity across your entire org. Self-hosted, Git-backed and MCP-native.

Protocols & Tool Integration TypeScript Listed Apache-2.0

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

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 24%
Last push yesterday
Compare Hexis

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Hexis scores 53.5/100 (Grade C), ranked #850 of 1346 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 3.7/10; 24% of recent commits are signed; last pushed 2026-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Hexis 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 Hexis and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run.

  1. Source Partly signed

    github.com/Bevel-Software/Hexis, Apache-2.0, last pushed 2026-10-02. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages None

    No registry package. Hexis 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-09-12 OSSF Scorecard: 4.1/10

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 Hexis’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 Hexis compares in Protocols & Tool Integration

  1. #41 Figma Context MCP 54.1 +0.6
  2. #42 Agent Reach 53.9 +0.4
  3. #43 Hexis 53.5 this agent
  4. #44 golf 52.9 −0.6
  5. #45 FastAPI-MCP 51.6 −1.9

Bars show each HVTrust score; the tick marks Hexis’s 53.5.

Where the 53.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

53.5 / 100 · 100.0% confidence

Hexis Protocols & Tool Integration average (62 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.8 / 25
4.6 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
1.2 below avg 12.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.0 above avg 13.9
AdoptionLog-scaled stars · package downloads
4.7 / 20
6.0 below avg 10.7

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-03
Rank Moved
Rank dropped 13 spots (#837 → #850)
2026-09-30
Rank Moved
Rank dropped 37 spots (#803 → #840)
2026-09-26
Rank Moved
Rank rose 10 spots (#806 → #796)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Hexis View Protocols & Tool Integration Report missing data
66.2
Activity sub-score · out of 100
#43
In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-03 16:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-03

Activity & Reach

Stars
91
Forks
8
Last Push
2026-10-02
yesterday
Commits (4 wk)
1238
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼13
was #837

Analysis

Activity Inputs

66.2 / 100
StarsRepository reach
11.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
4.4 / 20

Common questions about Hexis

Public trust evidence for Hexis 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 Hexis publish package provenance?
No published build provenance is currently detected for Hexis. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Hexis have an OpenSSF Scorecard?
Hexis has an OpenSSF Scorecard score of 3.7/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 Hexis actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Hexis use?
Hexis ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hexis's commits signed?
24% of the last 100 commits to Hexis 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
Hexis appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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
How this surface has changed

Detected changes to Hexis'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Hexis?

For maintainers

HVTrust scores Hexis 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
Rank 19Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-03
Rank Moved
Rank dropped 13 spots (#837 → #850)
2026-09-30
Rank Moved
Rank dropped 37 spots (#803 → #840)
2026-09-26
Rank Moved
Rank rose 10 spots (#806 → #796)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 353 spots (#450 → #803)
2026-09-23
HVTrust Changed
HVTrust up 10.3pts (44.1 → 54.4)
2026-09-22
Newly Listed
First tracked at rank #450
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Scorecard Added
OSSF Scorecard: 4.1/10
2026-09-12
Grade Changed
Trust grade D → C
2026-09-12
Rank Moved
Rank rose 523 spots (#1309 → #786)
2026-09-12
HVTrust Changed
HVTrust up 31.6pts (23.2 → 54.8)
2026-09-08
Rank Moved
Rank dropped 14 spots (#1295 → #1309)
2026-09-05
Rank Moved
Rank dropped 13 spots (#1270 → #1283)
2026-09-04
Rank Moved
Rank dropped 12 spots (#1258 → #1270)
2026-09-03
Rank Moved
Rank dropped 25 spots (#1233 → #1258)
2026-09-02
Rank Moved
Rank dropped 35 spots (#1198 → #1233)
2026-09-01
Rank Moved
Rank dropped 38 spots (#1160 → #1198)
2026-08-31
Rank Moved
Rank dropped 23 spots (#1137 → #1160)
2026-08-30
Rank Moved
Rank dropped 36 spots (#1101 → #1137)
2026-08-29
Rank Moved
Rank dropped 36 spots (#1065 → #1101)
2026-08-28
Rank Moved
Rank dropped 28 spots (#1037 → #1065)
2026-08-27
Rank Moved
Rank dropped 19 spots (#1018 → #1037)
2026-08-26
Rank Moved
Rank dropped 90 spots (#928 → #1018)
2026-08-22
Rank Moved
Rank rose 12 spots (#938 → #926)
2026-08-19
Rank Moved
Rank dropped 16 spots (#914 → #930)
2026-08-16
Newly Listed
First tracked at rank #930
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/hexis.svg)](https://hvtracker.net/agents/hexis)
HTML:
<a href="https://hvtracker.net/agents/hexis"><img src="https://hvtracker.net/badge/hexis.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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