updated 2026-11-05 12:09 UTC

HexStrike AI

Repository Website

HexStrike AI MCP Agents is an advanced MCP server that lets AI agents (Claude, GPT, Copilot, etc.) autonomously run 150+ cybersecurity tools for automated pentesting, vulnerability discovery, bug bounty automation, and security research. Seamlessly bridge LLMs with real-world offensive security…

Security & Guardrails Python Listed MIT

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

OSSF Scorecard 1.5 / 10
Provenance None
Signed commits 5%
Last push 94d ago
Compare HexStrike AI

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →
Suggest a correction

In detail: HexStrike AI scores 40.0/100 (Grade D), ranked #1203 of 1374 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.5/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 →

How HexStrike AI 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 HexStrike AI 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 Partly signed

    github.com/0x4m4/hexstrike-ai, MIT, last pushed 2026-08-03. 5% 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 1.5/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages None

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

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of HexStrike AI.

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 HexStrike AI’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 HexStrike AI compares in Security & Guardrails

  1. #22 Cybermes 49.4 +9.4
  2. #23 Anything Analyzer 46.8 +6.8
  3. #24 auto-re-agent 43.1 +3.1
  4. #25 AutoCVE 42.8 +2.8
  5. #26 HexStrike AI 40.0 this agent

Bars show each HVTrust score; the tick marks HexStrike AI’s 40.0.

Where the 40.0 comes from

HVTrust dimensions vs the Security & Guardrails average

40.0 / 100 · 100.0% confidence

HexStrike AI Security & Guardrails average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.1 / 25
8.3 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
9.8 / 17
2.9 below avg 12.7
Maintenance60% last-push freshness · 40% commit activity
5.7 / 20
9.2 below avg 14.9
AdoptionLog-scaled stars · package downloads
9.9 / 20
in line with avg 10.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-01
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 11 spots (#1142 → #1153)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.5/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.
Refresh maintenance signals The repo was last pushed 94 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Security & Guardrails Report missing data
52.9
Activity sub-score · out of 100
#26
In Security & Guardrails

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-11-05 12:09 UTC · Repo last pushed 94 days ago

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
13.4k
Forks
2.7k
Last Push
2026-08-03
94 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
67
Rank Change
=
was #1203

Analysis

Activity Inputs

52.9 / 100
StarsRepository reach
24.8 / 30
FreshnessLast push recency
11.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.0 / 20

Common questions about HexStrike AI

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.5/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?
Slowing down. Last push was 94 days ago — keep an eye on whether activity resumes.
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
1 tags
Broad capability areas 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-11-01
Activity Went Stale
No commits for 90 days
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 29Surface 1Stale 1
2026-11-01
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 11 spots (#1142 → #1153)
2026-09-23
Rank Moved
Rank dropped 630 spots (#475 → #1105)
2026-09-22
Rank Moved
Rank dropped 103 spots (#372 → #475)
2026-09-21
Rank Moved
Rank rose 728 spots (#1100 → #372)
2026-09-17
Rank Moved
Rank dropped 10 spots (#1085 → #1095)
2026-09-16
Rank Moved
Rank rose 12 spots (#1097 → #1085)
2026-09-12
Rank Moved
Rank dropped 15 spots (#1078 → #1093)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1058 → #1074)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1048 → #1058)
2026-09-07
Rank Moved
Rank dropped 33 spots (#1015 → #1048)
2026-09-06
Rank Moved
Rank dropped 18 spots (#997 → #1015)
2026-09-05
Rank Moved
Rank dropped 49 spots (#948 → #997)
2026-09-04
Rank Moved
Rank dropped 22 spots (#926 → #948)
2026-09-03
Rank Moved
Rank dropped 55 spots (#871 → #926)
2026-09-02
Rank Moved
Rank dropped 78 spots (#793 → #871)
2026-09-01
Rank Moved
Rank dropped 30 spots (#763 → #793)
2026-08-31
Rank Moved
Rank dropped 37 spots (#726 → #763)
2026-08-30
Rank Moved
Rank dropped 25 spots (#701 → #726)
2026-08-29
Rank Moved
Rank dropped 46 spots (#655 → #701)
2026-08-28
Rank Moved
Rank dropped 21 spots (#634 → #655)
2026-08-27
Rank Moved
Rank dropped 16 spots (#618 → #634)
2026-08-26
Rank Moved
Rank dropped 96 spots (#522 → #618)
2026-08-24
Rank Moved
Rank dropped 15 spots (#506 → #521)
2026-08-22
Rank Moved
Rank rose 11 spots (#521 → #510)
2026-08-19
Rank Moved
Rank dropped 12 spots (#508 → #520)
2026-08-13
Rank Moved
Rank dropped 14 spots (#490 → #504)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Rank Moved
Rank rose 20 spots (#510 → #490)
2026-08-10
Rank Moved
Rank dropped 18 spots (#492 → #510)
2026-08-08
Rank Moved
Rank dropped 129 spots (#355 → #484)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.0 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.4 · Raw JSON