updated 2026-08-25 05:32 UTC

Agent-E

EmergenceAI/agent-e

Agent driven automation starting with the web. Try it: https://www.emergence.ai/web-automation-api

Browser & Computer Use Python Grade D Listed MIT
37.8/100
Rank #671 of 1308
Compare Agent-E

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-05-04 · 113d ago
Recent change
No recent signal change

Is Agent-E safe? Agent-E scores 37.8/100 (Grade D), ranked #671 of 1308 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 3.6/10; 36% of recent commits are signed; last pushed 2026-05-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#27 UI-TARS — 39.9 (D) → #28 Understudy — 39.2 (D) → #30 OpenCUA — 36.3 (D) → #31 OpenAI CUA Sample App — 36.0 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-16
Rank Moved
Rank dropped 10 spots (#651 → #661)
2026-08-10
Rank Moved
Rank dropped 24 spots (#620 → #644)
2026-08-08
Rank Moved
Rank dropped 224 spots (#395 → #619)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
Refresh maintenance signals The repo was last pushed 113 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Agent-E View Browser & Computer Use Report missing data
38.6
Activity sub-score · out of 100
#29
In Browser & Computer Use

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 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-08-25 05:32 UTC · Repo last pushed 113 days ago

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
1.2k
Forks
190
Last Push
2026-05-04
113 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
0
Open Issues
17
Rank Change
▲1
was #672

Analysis

HVTrust Dimensions vs Browser & Computer Use

37.8 / 100 · 100.0% confidence

Agent-E Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
1.2 below avg 7.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
0.8 above avg 10.8
Maintenance60% last-push freshness · 40% commit activity
4.5 / 20
8.3 below avg 12.8
AdoptionLog-scaled stars · package downloads
7.4 / 20
3.9 below avg 11.3

Activity Inputs

38.6 / 100
StarsRepository reach
18.6 / 30
FreshnessLast push recency
9.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.6 / 20

Supply Chain Trust

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

Is Agent-E safe?

Public trust evidence for Agent-E 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 Agent-E publish package provenance?
No published build provenance is currently detected for Agent-E. 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-E have an OpenSSF Scorecard?
Agent-E has an OpenSSF Scorecard score of 3.6/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-E actively maintained?
Slowing down. Last push was 113 days ago — keep an eye on whether activity resumes.
What license does Agent-E use?
Agent-E ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agent-E's commits signed?
36% of the last 100 commits to Agent-E 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 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 Agent-E'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-02
Activity Went Stale
No commits for 90 days

Maintain Agent-E?

For maintainers

HVTrust scores Agent-E 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
Rank 13HVTrust 1Stale 1
2026-08-16
Rank Moved
Rank dropped 10 spots (#651 → #661)
2026-08-10
Rank Moved
Rank dropped 24 spots (#620 → #644)
2026-08-08
Rank Moved
Rank dropped 224 spots (#395 → #619)
2026-08-02
Activity Went Stale
No commits for 90 days
2026-07-15
Rank Moved
Rank dropped 24 spots (#346 → #370)
2026-07-14
Rank Moved
Rank dropped 19 spots (#327 → #346)
2026-07-13
Rank Moved
Rank dropped 36 spots (#291 → #327)
2026-06-24
Rank Moved
Rank dropped 31 spots (#230 → #261)
2026-06-23
Rank Moved
Rank dropped 18 spots (#212 → #230)
2026-06-22
Rank Moved
Rank dropped 10 spots (#202 → #212)
2026-06-21
Rank Moved
Rank dropped 12 spots (#190 → #202)
2026-06-18
Rank Moved
Rank dropped 13 spots (#171 → #184)
2026-06-02
Rank Moved
Rank dropped 10 spots (#141 → #151)
2026-06-01
Rank Moved
Rank dropped 18 spots (#123 → #141)
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (37.3 → 47.2)
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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