Is Agent Reach safe to use?

Agent Reach has an HVTrust score of 58.4/100 (Grade C), ranked #357 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Agent Reach?

Agent Reach scores 58.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 70.7k GitHub stars and is categorized under Protocols & Tool Integration.

Agent Reach

Panniantong/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

58.4/100

Rank #357 of 1283

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-08-06 · 5d ago

Recent change

Rank +3

Is Agent Reach safe? Agent Reach scores 58.4/100 (Grade C), ranked #357 of 1283 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; recent commits are unsigned; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#24 n8n-MCP — 62.6 (C) → #25 MCP Go — 60.5 (C) → #27 Figma Context MCP — 55.4 (C) → #28 MCP Bundles — 54.0 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

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.

Compare with another agent Get email alerts for Agent Reach View Protocols & Tool Integration Report missing data

93.1

Activity sub-score · out of 100

#26

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 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 →

Activity & Reach

Stars

70.7k

Forks

6.0k

Last Push

2026-08-06

5 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

Rank Change

▼1

was #356

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

58.4 / 100 · 100.0% confidence

Agent Reach Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.0 / 25

2.6 below avg 8.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

1.2 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

18.7 / 20

4.9 above avg 13.8

AdoptionLog-scaled stars · package downloads

11.6 / 20

1.2 above avg 10.4

Activity Inputs

93.1 / 100

StarsRepository reach

29.1 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

22.1 / 25

CommunityFork signal

17.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

—

Unable to query

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?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Agent Reach use?

Agent Reach ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

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)

2026-06-16

Newly Listed

First tracked at rank #204

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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