updated 2026-10-09 20:07 UTC

AdalFlow

Repository Website

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

Agent Frameworks Python Listed MIT

Is AdalFlow safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.3 / 10
Provenance None
Signed commits 32%
Last push 133d ago
Advisories None known
Compare AdalFlow

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: AdalFlow scores 43.3/100 (Grade D), ranked #1129 of 1371 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; no published advisory affects its latest release (adalflow); last pushed 2026-05-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How AdalFlow 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 AdalFlow 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 Partly signed

    github.com/SylphAI-Inc/AdalFlow, MIT, last pushed 2026-05-29. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review10
    • Branch Protection1
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    • PyPI adalflow Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: adalflow 1.1.3. 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 AdalFlow.

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 AdalFlow’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 AdalFlow compares in Agent Frameworks

  1. #99 agentUniverse 44.6 +1.3
  2. #100 Fedml 44.4 +1.1
  3. #101 AdalFlow 43.3 this agent
  4. #102 PocketFlow 42.4 −0.9
  5. #103 omniclaw 41.2 −2.1

Bars show each HVTrust score; the tick marks AdalFlow’s 43.3.

Where the 43.3 comes from

HVTrust dimensions vs the Agent Frameworks average

43.3 / 100 · 100.0% confidence

AdalFlow Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
3.9 below avg 9.6
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
1.0 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
3.1 / 20
11.3 below avg 14.4
AdoptionLog-scaled stars · package downloads
12.7 / 20
1.5 above avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1118 → #1129)
2026-09-23
Rank Moved
Rank dropped 631 spots (#444 → #1075)
2026-09-22
Rank Moved
Rank dropped 81 spots (#363 → #444)
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 133 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for AdalFlow View Agent Frameworks Report missing data
40.3
Activity sub-score · out of 100
#101
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 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-10-09 20:07 UTC · Repo last pushed 133 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
4.2k
Forks
388
Last Push
2026-05-29
133 days ago
Commits (4 wk)
0
Downloads (7d)
919
pypi
HN mentions (30d)
0
Open Issues
35
Rank Change
▼11
was #1118

Analysis

Activity Inputs

40.3 / 100
StarsRepository reach
21.8 / 30
FreshnessLast push recency
6.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.0 / 20

Common questions about AdalFlow

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 133 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
How this surface has changed

Detected changes to AdalFlow'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-27
Activity Went Stale
No commits for 90 days

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 34Grade 1Stale 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1118 → #1129)
2026-09-23
Rank Moved
Rank dropped 631 spots (#444 → #1075)
2026-09-22
Rank Moved
Rank dropped 81 spots (#363 → #444)
2026-09-21
Rank Moved
Rank rose 706 spots (#1069 → #363)
2026-09-17
Rank Moved
Rank dropped 10 spots (#1050 → #1060)
2026-09-12
Rank Moved
Rank dropped 13 spots (#1037 → #1050)
2026-09-09
Rank Moved
Rank dropped 17 spots (#1014 → #1031)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1003 → #1014)
2026-09-07
Rank Moved
Rank dropped 31 spots (#972 → #1003)
2026-09-06
Rank Moved
Rank dropped 15 spots (#957 → #972)
2026-09-05
Rank Moved
Rank dropped 50 spots (#907 → #957)
2026-09-04
Rank Moved
Rank dropped 29 spots (#878 → #907)
2026-09-03
Rank Moved
Rank dropped 63 spots (#815 → #878)
2026-09-02
Rank Moved
Rank dropped 46 spots (#769 → #815)
2026-09-01
Rank Moved
Rank dropped 31 spots (#738 → #769)
2026-08-31
Rank Moved
Rank dropped 34 spots (#704 → #738)
2026-08-30
Rank Moved
Rank dropped 24 spots (#680 → #704)
2026-08-29
Rank Moved
Rank dropped 46 spots (#634 → #680)
2026-08-28
Rank Moved
Rank dropped 21 spots (#613 → #634)
2026-08-27
Activity Went Stale
No commits for 90 days
2026-08-27
Rank Moved
Rank dropped 13 spots (#600 → #613)
2026-08-26
Rank Moved
Rank dropped 89 spots (#511 → #600)
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)
GitHub → Website → PyPI: adalflow

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.3 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.4 · Raw JSON