Agent Reach

Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongSh

Protocols & Tool Integration Python Grade C Listed MIT
55.0/100
Rank #770 of 1328
Compare Agent Reach

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-01 · 14d ago
Recent change
Rank +1

Is Agent Reach safe? Agent Reach scores 55.0/100 (Grade C), ranked #770 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 33% of recent commits are signed; last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-11
Rank Moved
Rank dropped 34 spots (#723 → #757)
2026-09-09
Rank Moved
Rank rose 46 spots (#762 → #716)
2026-09-07
Rank Moved
Rank dropped 43 spots (#712 → #755)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
78.1
Activity sub-score · out of 100
#42

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 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-09-15 03:32 UTC · Repo last pushed 14 days ago

Rank Trend

2026-08-11 2026-09-15

Activity & Reach

Stars
81.4k
Forks
7.1k
Last Push
2026-09-01
14 days ago
Commits (4 wk)
3
Downloads (7d)
HN mentions (30d)
55
Open Issues
78
Rank Change
▲1
was #771

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

55.0 / 100 · 100.0% confidence

Agent Reach Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.6 / 25
2.9 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.7
Maintenance60% last-push freshness · 40% commit activity
13.5 / 20
0.7 below avg 14.2
AdoptionLog-scaled stars · package downloads
11.8 / 20
1.2 above avg 10.6

Activity Inputs

78.1 / 100
StarsRepository reach
29.5 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
17.9 / 20

Supply Chain Trust

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

Is Agent Reach safe?

Agent Reach has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Agent Reach publish package provenance?
No published build provenance is currently detected for Agent Reach. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Agent Reach have an OpenSSF Scorecard?
Agent Reach has an OpenSSF Scorecard score of 4.8/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 Agent Reach actively maintained?
Maintained. Last push was 14 days ago.
What license does Agent Reach use?
Agent Reach ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agent Reach's commits signed?
33% of the last 100 commits to Agent Reach 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium 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

Maintain Agent Reach?

For maintainers

HVTrust scores Agent Reach 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 33HVTrust 3Grade 1Scorecard 1Score 1
2026-09-11
Rank Moved
Rank dropped 34 spots (#723 → #757)
2026-09-09
Rank Moved
Rank rose 46 spots (#762 → #716)
2026-09-07
Rank Moved
Rank dropped 43 spots (#712 → #755)
2026-09-06
Rank Moved
Rank dropped 68 spots (#644 → #712)
2026-09-05
Rank Moved
Rank dropped 175 spots (#469 → #644)
2026-09-05
HVTrust Changed
HVTrust down 3.4pts (59.6 → 56.2)
2026-09-05
Activity Score Changed
Activity score down 10pts (92 → 81)
2026-09-04
Rank Moved
Rank dropped 12 spots (#457 → #469)
2026-09-03
Rank Moved
Rank rose 15 spots (#472 → #457)
2026-09-02
Rank Moved
Rank dropped 14 spots (#458 → #472)
2026-08-31
Rank Moved
Rank dropped 32 spots (#424 → #456)
2026-08-30
Rank Moved
Rank rose 12 spots (#436 → #424)
2026-08-29
Rank Moved
Rank dropped 15 spots (#421 → #436)
2026-08-27
Rank Moved
Rank dropped 11 spots (#405 → #416)
2026-08-26
Rank Moved
Rank dropped 42 spots (#363 → #405)
2026-08-25
Rank Moved
Rank rose 13 spots (#376 → #363)
2026-08-24
Rank Moved
Rank dropped 19 spots (#357 → #376)
2026-08-22
Rank Moved
Rank rose 16 spots (#364 → #348)
2026-08-19
Rank Moved
Rank dropped 15 spots (#349 → #364)
2026-08-17
Rank Moved
Rank rose 15 spots (#365 → #350)
2026-08-13
Rank Moved
Rank dropped 15 spots (#338 → #353)
2026-08-12
Rank Moved
Rank rose 19 spots (#357 → #338)
2026-08-10
Rank Moved
Rank dropped 17 spots (#339 → #356)
2026-08-08
Rank Moved
Rank dropped 83 spots (#253 → #336)
2026-08-06
Rank Moved
Rank rose 17 spots (#239 → #222)
2026-08-04
Rank Moved
Rank rose 13 spots (#248 → #235)
2026-07-29
Rank Moved
Rank dropped 11 spots (#227 → #238)
2026-07-26
Rank Moved
Rank rose 11 spots (#227 → #216)
2026-07-24
Rank Moved
Rank rose 14 spots (#250 → #236)
2026-07-15
Rank Moved
Rank dropped 11 spots (#229 → #240)
2026-07-14
Rank Moved
Rank dropped 15 spots (#214 → #229)
2026-07-13
Rank Moved
Rank dropped 28 spots (#186 → #214)
2026-06-24
Rank Moved
Rank dropped 24 spots (#162 → #186)
2026-06-20
Rank Moved
Rank dropped 17 spots (#128 → #145)
2026-06-20
HVTrust Changed
HVTrust down 3.5pts (62.3 → 58.8)
2026-06-18
Scorecard Added
OSSF Scorecard: 5.0/10
2026-06-18
Grade Changed
Trust grade D → C
2026-06-18
Rank Moved
Rank rose 80 spots (#206 → #126)
2026-06-18
HVTrust Changed
HVTrust up 27.9pts (34.5 → 62.4)

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON