HexStrike AI

HexStrike AI MCP Agents is an advanced MCP server that lets AI agents (Claude, GPT, Copilot, etc.) autonomously run 150+

Security & Guardrails Python Grade D Listed MIT
46.1/100
Rank #342 of 468
Compare HexStrike AI

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
2026-08-03 · 3d ago
Recent change
Fresh +3

Is HexStrike AI safe? HexStrike AI scores 46.1/100 (Grade D), ranked #342 of 468 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.6/10; 5% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-03
Activity Resumed
Activity resumed
2026-08-03
Rank Moved
Rank rose 36 spots (#379 → #343)
2026-08-03
HVTrust Changed
HVTrust up 7.1pts (39.2 → 46.3)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.6/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.
68.3
Activity sub-score · out of 100
#12

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 →

Signals refreshed 2026-08-06 05:00 UTC · Repo last pushed 3 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
10.8k
Forks
2.3k
Last Push
2026-08-03
3 days ago
Commits (4 wk)
1?
Downloads (7d)
HN mentions (30d)
Open Issues
58
Rank Change
=
was #342

Analysis

HVTrust Dimensions vs Security & Guardrails

46.1 / 100 · 100.0% confidence

HexStrike AI Security & Guardrails average (14 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.2 / 25
6.8 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
9.9 / 17
2.5 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
12.4 / 20
4.2 below avg 16.6
AdoptionLog-scaled stars · package downloads
9.7 / 20
1.0 below avg 10.7

Activity Inputs

68.3 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
15.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
1.6 / 10
OpenSSF Scorecard · scanned Aug 6, 2026
Signed Commits
5%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 1
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Is HexStrike AI safe?

Public trust evidence for HexStrike AI 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 HexStrike AI publish package provenance?
No published build provenance is currently detected for HexStrike AI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does HexStrike AI have an OpenSSF Scorecard?
HexStrike AI has an OpenSSF Scorecard score of 1.6/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 HexStrike AI actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does HexStrike AI use?
HexStrike AI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are HexStrike AI's commits signed?
4% of the last 100 commits to HexStrike AI 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
HexStrike AI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
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 HexStrike AI'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-08-03
Activity Resumed
Activity resumed
2026-07-26
Activity Went Stale
No commits for 90 days
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Postgres

Maintain HexStrike AI?

For maintainers

HVTrust scores HexStrike AI 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

Signal history
Rank 8HVTrust 2Listed 1Scorecard 1Surface 1Stale 1Score 1Fresh 1
2026-08-03
Activity Resumed
Activity resumed
2026-08-03
Rank Moved
Rank rose 36 spots (#379 → #343)
2026-08-03
HVTrust Changed
HVTrust up 7.1pts (39.2 → 46.3)
2026-08-03
Activity Score Changed
Activity score up 17pts (51 → 69)
2026-07-29
Rank Moved
Rank dropped 10 spots (#367 → #377)
2026-07-26
Activity Went Stale
No commits for 90 days
2026-07-15
Rank Moved
Rank dropped 25 spots (#334 → #359)
2026-07-14
Rank Moved
Rank dropped 19 spots (#315 → #334)
2026-07-13
Rank Moved
Rank dropped 36 spots (#279 → #315)
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Postgres
2026-06-24
Rank Moved
Rank dropped 33 spots (#248 → #281)
2026-06-23
Scorecard Added
OSSF Scorecard: 1.8/10
2026-06-23
Rank Moved
Rank rose 43 spots (#291 → #248)
2026-06-23
HVTrust Changed
HVTrust up 22.4pts (18.7 → 41.1)
2026-06-21
Rank Moved
Rank dropped 28 spots (#262 → #290)
2026-06-20
Newly Listed
First tracked at rank #262

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/hexstrike-ai.svg)](https://hvtracker.net/agents/hexstrike-ai)
HTML:
<a href="https://hvtracker.net/agents/hexstrike-ai"><img src="https://hvtracker.net/badge/hexstrike-ai.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

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