AutoAgent

"AutoAgent: Fully-Automated and Zero-Code LLM Agent Framework"

Agent Frameworks Python Grade D Listed MIT
31.3/100
Rank #409 of 468
Compare AutoAgent

How does it stack up against its Agent Frameworks 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
2025-10-16 · 294d ago
Recent change
No recent signal change

Is AutoAgent safe? AutoAgent scores 31.3/100 (Grade D), ranked #409 of 468 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 1.9/10; 37% of recent commits are signed; last pushed 2025-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-29
Rank Moved
Rank dropped 12 spots (#398 → #410)
2026-07-15
Rank Moved
Rank dropped 24 spots (#368 → #392)
2026-07-14
Rank Moved
Rank dropped 21 spots (#347 → #368)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.9/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 294 days ago. Fresh activity helps separate stable projects from stale ones.
38.5
Activity sub-score · out of 100
#84

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-06 05:00 UTC · Repo last pushed 294 days ago — may be stale

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
9.7k
Forks
1.4k
Last Push
2025-10-16
294 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
55
Rank Change
=
was #409

Analysis

HVTrust Dimensions vs Agent Frameworks

31.3 / 100 · 100.0% confidence

AutoAgent Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.2 / 25
4.8 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
10.1 / 17
1.9 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.6 below avg 14.6
AdoptionLog-scaled stars · package downloads
9.6 / 20
2.3 below avg 11.9

Activity Inputs

38.5 / 100
StarsRepository reach
23.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.6 / 20

Supply Chain Trust

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

Is AutoAgent safe?

Public trust evidence for AutoAgent 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 AutoAgent publish package provenance?
No published build provenance is currently detected for AutoAgent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AutoAgent have an OpenSSF Scorecard?
AutoAgent has an OpenSSF Scorecard score of 1.9/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 AutoAgent actively maintained?
Stale. The repository has not been pushed to in 294 days. Consider whether the project is still being maintained.
What license does AutoAgent use?
AutoAgent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AutoAgent's commits signed?
37% of the last 100 commits to AutoAgent 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
Declared
Declared plugin/integration surface detected.
  • code
  • search
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 AutoAgent?

For maintainers

HVTrust scores AutoAgent 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 8Listed 1HVTrust 1Scorecard 1
2026-07-29
Rank Moved
Rank dropped 12 spots (#398 → #410)
2026-07-15
Rank Moved
Rank dropped 24 spots (#368 → #392)
2026-07-14
Rank Moved
Rank dropped 21 spots (#347 → #368)
2026-07-13
Rank Moved
Rank dropped 35 spots (#312 → #347)
2026-06-24
Rank Moved
Rank dropped 35 spots (#269 → #304)
2026-06-23
Rank Moved
Rank dropped 23 spots (#246 → #269)
2026-06-22
Scorecard Added
OSSF Scorecard: 1.9/10
2026-06-22
Rank Moved
Rank rose 54 spots (#300 → #246)
2026-06-22
HVTrust Changed
HVTrust up 19.3pts (15.3 → 34.6)
2026-06-21
Rank Moved
Rank dropped 31 spots (#269 → #300)
2026-06-20
Newly Listed
First tracked at rank #269

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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