updated 2026-11-11 00:08 UTC

earshot

Repository by Leonxlnx

Ears for coding agents: let AI hear, review and make sound. CPU-only, open source.

Protocols & Tool Integration Python Listed MIT

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

OSSF Scorecard No result
Provenance None
Signed commits 26%
Last push 5d ago
Compare earshot

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

Pick any agent to compare →
Suggest a correction

In detail: earshot scores 25.0/100 (Grade D), ranked #1366 of 1387 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 26% of recent commits are signed; last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How earshot 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 earshot 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/Leonxlnx/earshot, MIT, last pushed 2026-11-06. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

    No registry package. earshot 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 earshot.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues earshot’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 earshot compares in Protocols & Tool Integration

  1. #60 MCP Hub for Neovim 36.1 +11.1
  2. #61 TUUI 33.9 +8.9
  3. #62 Scira MCP Chat 30.7 +5.7
  4. #63 MCP Hub 30.4 +5.4
  5. #64 earshot 25.0 this agent

Bars show each HVTrust score; the tick marks earshot’s 25.0.

Where the 25.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

25.0 / 100 · 50.0% confidence

earshot Protocols & Tool Integration average (64 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.3 / 25
9.7 below avg 11.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.2 below avg 12.0
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
4.5 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
18.5 / 20
3.9 above avg 14.6
AdoptionLog-scaled stars · package downloads
8.8 / 20
2.3 below avg 11.1

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #1366
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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
View Protocols & Tool Integration Report missing data
79.1
Activity sub-score · out of 100
#64
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 5 days ago

Activity & Reach

Stars
4.5k
Forks
287
Last Push
2026-11-06
5 days ago
Commits (4 wk)
51
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #1366

Analysis

Activity Inputs

79.1 / 100
StarsRepository reach
21.9 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
21.4 / 25
CommunityFork signal
11.4 / 20

Common questions about earshot

Public trust evidence for earshot 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 earshot publish package provenance?
No published build provenance is currently detected for earshot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does earshot have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for earshot. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is earshot actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does earshot use?
earshot ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are earshot's commits signed?
25% of the last 100 commits to earshot 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
earshot 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
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 earshot?

For maintainers

HVTrust scores earshot 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
Listed 1
2026-11-10
Newly Listed
First tracked at rank #1366
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON