AdalFlow

AdalFlow: The library to build & auto-optimize LLM applications.

Agent Frameworks Python Grade D Listed MIT
46.5/100
Rank #512 of 1308
Compare AdalFlow

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 A · 4/5 signals
Last push
2026-05-29 · 88d ago
Recent change
Rank +2

Is AdalFlow safe? AdalFlow scores 46.5/100 (Grade D), ranked #512 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 32% of recent commits are signed; last pushed 2026-05-29. 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-08-24
Rank Moved
Rank dropped 17 spots (#486 → #503)
2026-08-22
Rank Moved
Rank rose 12 spots (#489 → #477)
2026-08-19
Rank Moved
Rank dropped 14 spots (#476 → #490)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/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 88 days ago. Fresh activity helps separate stable projects from stale ones.
46.5
Activity sub-score · out of 100
#72

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

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
4.2k
Forks
387
Last Push
2026-05-29
88 days ago
Commits (4 wk)
0
Downloads (7d)
1,492
pypi
HN mentions (30d)
0
Open Issues
33
Rank Change
▼9
was #503

Analysis

HVTrust Dimensions vs Agent Frameworks

46.5 / 100 · 100.0% confidence

AdalFlow Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
2.4 below avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
in line with avg 11.5
Maintenance60% last-push freshness · 40% commit activity
6.1 / 20
8.1 below avg 14.2
AdoptionLog-scaled stars · package downloads
12.9 / 20
1.6 above avg 11.3

Activity Inputs

46.5 / 100
StarsRepository reach
21.7 / 30
FreshnessLast push recency
12.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.0 / 20

Supply Chain Trust

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

Is AdalFlow safe?

Public trust evidence for AdalFlow 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 AdalFlow publish package provenance?
No published build provenance is currently detected for AdalFlow. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AdalFlow have an OpenSSF Scorecard?
AdalFlow has an OpenSSF Scorecard score of 3.3/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 AdalFlow actively maintained?
Slowing down. Last push was 88 days ago — keep an eye on whether activity resumes.
What license does AdalFlow use?
AdalFlow ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AdalFlow's commits signed?
32% of the last 100 commits to AdalFlow 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
9 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.
  • database
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

Maintain AdalFlow?

For maintainers

HVTrust scores AdalFlow 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 17Score 2Grade 1
2026-08-24
Rank Moved
Rank dropped 17 spots (#486 → #503)
2026-08-22
Rank Moved
Rank rose 12 spots (#489 → #477)
2026-08-19
Rank Moved
Rank dropped 14 spots (#476 → #490)
2026-08-17
Rank Moved
Rank rose 14 spots (#487 → #473)
2026-08-16
Rank Moved
Rank dropped 11 spots (#476 → #487)
2026-08-13
Rank Moved
Rank dropped 17 spots (#458 → #475)
2026-08-12
Rank Moved
Rank rose 12 spots (#470 → #458)
2026-08-10
Rank Moved
Rank dropped 17 spots (#454 → #471)
2026-08-08
Rank Moved
Rank dropped 113 spots (#336 → #449)
2026-07-29
Rank Moved
Rank dropped 11 spots (#315 → #326)
2026-07-15
Rank Moved
Rank dropped 23 spots (#281 → #304)
2026-07-14
Grade Changed
Trust grade C → D
2026-07-14
Rank Moved
Rank dropped 14 spots (#267 → #281)
2026-07-13
Rank Moved
Rank dropped 31 spots (#236 → #267)
2026-06-24
Rank Moved
Rank dropped 32 spots (#177 → #209)
2026-06-24
Activity Score Changed
Activity score down 5pts (68 → 63)
2026-06-18
Rank Moved
Rank dropped 12 spots (#141 → #153)
2026-06-01
Rank Moved
Rank dropped 12 spots (#97 → #109)
2026-05-29
Rank Moved
Rank dropped 20 spots (#79 → #99)
2026-05-28
Activity Score Changed
Activity score up 12pts (59 → 70)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/adalflow.svg)](https://hvtracker.net/agents/adalflow)
HTML:
<a href="https://hvtracker.net/agents/adalflow"><img src="https://hvtracker.net/badge/adalflow.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.3 · Raw JSON