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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 286 days ago — may be stale
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
1.4k
Forks
113
Last Push
2025-08-22
286 days ago
Commits (4 wk)
0
Downloads (7d)
1,758
pypi
HN mentions (30d)
0
Open Issues
40
Rank Change
▼9
was #145
Analysis
HVTrust Dimensions
47.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
11.9 / 20
Activity Inputs
28.5 / 100
StarsRepository reach
18.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.6 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
29%
of last 100 commits verified
Is ControlFlow safe?
Public trust evidence for ControlFlow 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 ControlFlow publish package provenance?
Yes. ControlFlow's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ControlFlow have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for ControlFlow. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is ControlFlow actively maintained?
Stale. The repository has not been pushed to in 286 days. Consider whether the project is still being maintained.
What license does ControlFlow use?
ControlFlow ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ControlFlow's commits signed?
28% of the last 100 commits to ControlFlow 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 ControlFlow?
HVTrust scores ControlFlow 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.
