Agent-S

Agent S: an open agentic framework that uses computers like a human

Browser & Computer Use Python Grade D Listed Apache-2.0
47.2/100
Rank #505 of 1308
Compare Agent-S

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 C · 2/5 signals
Last push
2026-08-01 · 18d ago
Recent change
Rank +3

Is Agent-S safe? Agent-S scores 47.2/100 (Grade D), ranked #505 of 1308 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.7/10; recent commits are unsigned; last pushed 2026-08-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-19
Rank Moved
Rank dropped 12 spots (#493 → #505)
2026-08-17
Rank Moved
Rank rose 10 spots (#503 → #493)
2026-08-16
Rank Moved
Rank dropped 10 spots (#493 → #503)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
67.7
Activity sub-score · out of 100
#21

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-19 06:02 UTC · Repo last pushed 18 days ago

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
12.2k
Forks
1.4k
Last Push
2026-08-01
18 days ago
Commits (4 wk)
2
Downloads (7d)
HN mentions (30d)
Open Issues
22
Rank Change
▼12
was #493

Analysis

HVTrust Dimensions vs Browser & Computer Use

47.2 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
2.8 below avg 7.4
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.9 above avg 10.7
Maintenance60% last-push freshness · 40% commit activity
12.7 / 20
in line with avg 13.0
AdoptionLog-scaled stars · package downloads
9.8 / 20
1.4 below avg 11.2

Activity Inputs

67.7 / 100
StarsRepository reach
24.5 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
14.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Aug 17, 2026
Signed Commits
Unable to query
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 3
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 1
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is Agent-S safe?

Public trust evidence for Agent-S 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-S publish package provenance?
No published build provenance is currently detected for Agent-S. 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-S have an OpenSSF Scorecard?
Agent-S has an OpenSSF Scorecard score of 3.7/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-S actively maintained?
Maintained. Last push was 18 days ago.
What license does Agent-S use?
Agent-S ships under Apache-2.0. 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
None detected
No MCP server signal detected.
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
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-S?

For maintainers

HVTrust scores Agent-S 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 16Score 6Grade 4Listed 2HVTrust 2Delisted 1Scorecard 1
2026-08-19
Rank Moved
Rank dropped 12 spots (#493 → #505)
2026-08-17
Rank Moved
Rank rose 10 spots (#503 → #493)
2026-08-16
Rank Moved
Rank dropped 10 spots (#493 → #503)
2026-08-13
Rank Moved
Rank dropped 15 spots (#477 → #492)
2026-08-10
Rank Moved
Rank dropped 17 spots (#460 → #477)
2026-08-08
Rank Moved
Rank dropped 116 spots (#339 → #455)
2026-08-01
Rank Moved
Rank rose 43 spots (#373 → #330)
2026-08-01
HVTrust Changed
HVTrust up 7.6pts (40.7 → 48.3)
2026-08-01
Activity Score Changed
Activity score up 17pts (53 → 70)
2026-07-15
Rank Moved
Rank dropped 27 spots (#326 → #353)
2026-07-14
Rank Moved
Rank dropped 15 spots (#311 → #326)
2026-07-13
Rank Moved
Rank dropped 37 spots (#274 → #311)
2026-06-24
Rank Moved
Rank dropped 33 spots (#220 → #253)
2026-06-23
Rank Moved
Rank dropped 17 spots (#203 → #220)
2026-06-21
Rank Moved
Rank dropped 11 spots (#183 → #194)
2026-06-20
Rank Moved
Rank dropped 11 spots (#172 → #183)
2026-06-18
Rank Moved
Rank dropped 12 spots (#155 → #167)
2026-06-16
Grade Changed
Trust grade C → D
2026-06-16
Activity Score Changed
Activity score down 7pts (67 → 59)
2026-06-15
Grade Changed
Trust grade D → C
2026-06-15
Activity Score Changed
Activity score up 7pts (60 → 67)
2026-06-13
Grade Changed
Trust grade C → D
2026-06-13
Activity Score Changed
Activity score down 7pts (67 → 60)
2026-06-11
Activity Score Changed
Activity score up 7pts (60 → 67)
2026-06-10
Scorecard Added
OSSF Scorecard: 3.9/10
2026-06-10
Grade Changed
Trust grade D → C
2026-06-10
Rank Moved
Rank rose 54 spots (#208 → #154)
2026-06-10
HVTrust Changed
HVTrust up 28.1pts (22.0 → 50.1)
2026-06-10
Activity Score Changed
Activity score down 7pts (67 → 60)
2026-06-08
Newly Listed
First tracked at rank #211
2026-06-07
Removed From Active Tracking
Removed from active tracking
2026-06-06
Newly Listed
First tracked at rank #208

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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