How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 6 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
4.2k
Forks
374
Last Push
2026-05-29
6 days ago
Commits (4 wk)
10
Downloads (7d)
5,823
pypi
HN mentions (30d)
0
Open Issues
63
Rank Change
▼10
was #116
Analysis
HVTrust Dimensions
58.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
6.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.8 / 17
MaintenanceFreshness and commits
15.8 / 20
AdoptionStars and downloads
13.7 / 20
Activity Inputs
70.9 / 100
StarsRepository reach
21.7 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
12.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.9 / 10
via deps.dev · OpenSSF
Signed Commits
32%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained8
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is AdalFlow safe?
AdalFlow has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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.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 AdalFlow actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain AdalFlow?
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.
