HyperAgent

AI Browser Automation

Needs review TypeScript Grade D Listed NOASSERTION
43.0/100
Rank #568 of 1283
Compare HyperAgent

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-05-11 · 92d ago
Recent change
Rank +2

Is HyperAgent safe? HyperAgent scores 43.0/100 (Grade D), ranked #568 of 1283 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 3.8/10; 51% of recent commits are signed; last pushed 2026-05-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Needs review

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 22 spots (#545 → #567)
2026-08-09
Activity Went Stale
No commits for 90 days
2026-08-08
Rank Moved
Rank dropped 166 spots (#376 → #542)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
Refresh maintenance signals The repo was last pushed 92 days ago. Fresh activity helps separate stable projects from stale ones.
42.2
Activity sub-score · out of 100
#9

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-08-11 21:02 UTC · Repo last pushed 92 days ago

Activity & Reach

Stars
1.5k
Forks
195
Last Push
2026-05-11
92 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
15
Rank Change
▼1
was #567

Analysis

HVTrust Dimensions vs Needs review

43.0 / 100 · 100.0% confidence

HyperAgent Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
in line with avg 7.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 10.8
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.6 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
5.9 / 20
8.8 below avg 14.7
AdoptionLog-scaled stars · package downloads
7.6 / 20
1.4 below avg 9.0

Activity Inputs

42.2 / 100
StarsRepository reach
19.1 / 30
FreshnessLast push recency
12.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.7 / 20

Supply Chain Trust

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

Is HyperAgent safe?

Public trust evidence for HyperAgent 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 HyperAgent publish package provenance?
No published build provenance is currently detected for HyperAgent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does HyperAgent have an OpenSSF Scorecard?
HyperAgent has an OpenSSF Scorecard score of 3.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 HyperAgent actively maintained?
Slowing down. Last push was 92 days ago — keep an eye on whether activity resumes.
What license does HyperAgent use?
HyperAgent ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are HyperAgent's commits signed?
51% of the last 100 commits to HyperAgent 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
HyperAgent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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 HyperAgent'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-08-09
Activity Went Stale
No commits for 90 days

Maintain HyperAgent?

For maintainers

HVTrust scores HyperAgent 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 10Listed 1HVTrust 1Scorecard 1Stale 1
2026-08-10
Rank Moved
Rank dropped 22 spots (#545 → #567)
2026-08-09
Activity Went Stale
No commits for 90 days
2026-08-08
Rank Moved
Rank dropped 166 spots (#376 → #542)
2026-07-29
Rank Moved
Rank dropped 11 spots (#350 → #361)
2026-07-15
Rank Moved
Rank dropped 25 spots (#315 → #340)
2026-07-14
Rank Moved
Rank dropped 17 spots (#298 → #315)
2026-07-13
Rank Moved
Rank dropped 35 spots (#263 → #298)
2026-06-24
Rank Moved
Rank dropped 32 spots (#222 → #254)
2026-06-23
Rank Moved
Rank dropped 18 spots (#204 → #222)
2026-06-21
Rank Moved
Rank dropped 10 spots (#185 → #195)
2026-06-19
Scorecard Added
OSSF Scorecard: 3.8/10
2026-06-19
Rank Moved
Rank rose 44 spots (#228 → #184)
2026-06-19
HVTrust Changed
HVTrust up 27.3pts (19.5 → 46.8)
2026-06-11
Newly Listed
First tracked at rank #220

Embed Badge Badge guide for maintainers →

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

Other agents in Needs review

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.3 · Raw JSON