Hermes Agent

The agent that grows with you

Coding Agents Python Grade A Listed MIT
Compare → Suggest correction
Listing state
Listed
HVTrust
81.0/100 · Grade A
Evidence coverage
Grade B · 3/5 signals
Last push
2026-07-19 · 0d ago
Recent change
No recent signal change

Is Hermes Agent safe? Hermes Agent scores 81.0/100 (Grade A), ranked #53 of 418 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.5/10; 28% of recent commits are signed; last pushed 2026-07-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Quick Trust Read

Verdict
Strong public trust posture, backed by multiple independent signals.
81.0/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
17.0/25
What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
100.0
Activity Score · out of 100
81.0
HVTrust Score · out of 100
#53
Global Rank · of 418
#5

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-07-19 12:00 UTC · Repo last pushed today

Rank Trend

2026-07-05 2026-07-19

Activity & Reach

Stars
217.1k
Forks
40.8k
Last Push
2026-07-19
today
Commits (4 wk)
4231
Downloads (7d)
78,325
npm+pypi
HN mentions (30d)
Open Issues
7455
Rank Change
=
was #53

Analysis

HVTrust Dimensions

81.0 / 100 · 100.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.0 / 25
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
Adoption60% stars · 40% downloads, log-scaled
19.3 / 20

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Supply Chain Trust

Package Provenance
Verified
npm, pypi attestation
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Jul 11, 2026
Signed Commits
28%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 3
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 10
Security-Policy 10
Signed-Releases 8
Token-Permissions 0
Vulnerabilities 0

Is Hermes Agent safe?

Public supply-chain signals for Hermes Agent are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Hermes Agent carries less obvious unverified-evidence risk than projects with thin signals.
Does Hermes Agent publish package provenance?
Yes. Hermes Agent's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Hermes Agent have an OpenSSF Scorecard?
Hermes Agent has an OpenSSF Scorecard score of 6.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 Hermes Agent actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Hermes Agent use?
Hermes Agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hermes Agent's commits signed?
28% of the last 100 commits to Hermes Agent 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.

Ranked neighbours in Coding Agents

AI agent 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
Hermes Agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • database
  • search
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Warning
1 package source mismatch detected
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 Hermes Agent'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-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Firecrawl, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-06-05
Provenance Added
Package provenance attestation detected

Maintain Hermes Agent?

HVTrust scores Hermes Agent 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

Listed 1Provenance 1Drift 1MCP 1Surface 1Surface 1HVTrust 1Rank 1Grade 1Scorecard 1
2026-06-10
Scorecard Added
OSSF Scorecard: 5.4/10
2026-06-10
Grade Changed
Trust grade B → A
2026-06-10
Rank Moved
Rank rose 26 spots (#48 → #22)
2026-06-10
HVTrust Changed
HVTrust up 12.5pts (74.8 → 87.3)
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Firecrawl, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-06-05
Provenance Added
Package provenance attestation detected
2026-06-04
Newly Listed
First tracked at rank #195

Embed Badge Badge guide for maintainers →

HVTrust 81.0 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/hermes-agent.svg)](https://hvtracker.net/agents/hermes-agent)
HTML:
<a href="https://hvtracker.net/agents/hermes-agent"><img src="https://hvtracker.net/badge/hermes-agent.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON