updated 2026-10-09 12:08 UTC

Agno

Repository Website

Build, run, and manage agent platforms.

Agent Frameworks Python Listed Apache-2.0

Is Agno safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.9 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Agno

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Agno scores 87.4/100 (Grade A), ranked #51 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.9/10; 100% of recent commits are signed; no published advisory affects its latest release (agno); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Agno could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Agno and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/agno-agi/agno, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Sep 30, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI agno Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: agno 3.1.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Agno.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Agno’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Agno compares in Agent Frameworks

  1. #7 Cloudflare Agents 89.7 +2.3
  2. #8 PydanticAI 88.3 +0.9
  3. #9 Agno 87.4 this agent
  4. #10 Threadplane 83.9 −3.5
  5. #11 LangChain 83.4 −4.0

Bars show each HVTrust score; the tick marks Agno’s 87.4.

Where the 87.4 comes from

HVTrust dimensions vs the Agent Frameworks average

87.4 / 100 · 100.0% confidence

Agno Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.6 / 25
9.0 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.4 above avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.7 above avg 14.3
AdoptionLog-scaled stars · package downloads
18.7 / 20
7.5 above avg 11.2

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 14 spots (#36 → #50)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Agno View Agent Frameworks Report missing data
95.4
Activity sub-score · out of 100
#9
In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 12:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
42.6k
Forks
6.1k
Last Push
2026-10-09
today
Commits (4 wk)
125
Downloads (7d)
483,631
pypi
HN mentions (30d)
287
Open Issues
867
Rank Change
▲2
was #53

Analysis

Activity Inputs

95.4 / 100
StarsRepository reach
27.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.6 / 20

Common questions about Agno

Public supply-chain signals for Agno are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Agno carries less obvious unverified-evidence risk than projects with thin signals.
Does Agno publish package provenance?
Yes. Agno's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Agno have an OpenSSF Scorecard?
Agno has an OpenSSF Scorecard score of 4.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 Agno actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Agno use?
Agno ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agno's commits signed?
100% of the last 100 commits to Agno 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
Agno appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
18 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
4 tags
Broad capability areas detected.
  • browser
  • code
  • database
  • search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Agno'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-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: E2B, SerpAPI
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Cohere, ElevenLabs, Google Gemini, Groq, Mistral AI, Multi-provider (LiteLLM)

Maintain Agno?

For maintainers

HVTrust scores Agno 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
Surface 1Surface 1Surface 1Rank 1
2026-09-23
Rank Moved
Rank dropped 14 spots (#36 → #50)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: E2B, SerpAPI
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Cohere, ElevenLabs, Google Gemini, Groq, Mistral AI, Multi-provider (LiteLLM)
GitHub → Website → PyPI: agno

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON