How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 50 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
58.7k
Forks
8.9k
Last Push
2026-04-15
50 days ago
Commits (4 wk)
0
Downloads (7d)
314,526
pypi
HN mentions (30d)
6
Open Issues
877
Rank Change
▼1
was #28
Analysis
HVTrust Dimensions
78.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.5 / 17
MaintenanceFreshness and commits
8.7 / 20
AdoptionStars and downloads
18.8 / 20
Activity Inputs
65.1 / 100
StarsRepository reach
28.6 / 30
FreshnessLast push recency
18.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
18.4 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.9 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review6
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained2
Packaging10
Pinned-Dependencies0
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is AutoGen safe?
Public supply-chain signals for AutoGen are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but AutoGen carries less obvious unverified-evidence risk than projects with thin signals.
Does AutoGen publish package provenance?
Yes. AutoGen's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does AutoGen have an OpenSSF Scorecard?
AutoGen has an OpenSSF Scorecard score of 5.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 AutoGen actively maintained?
Slowing down. Last push was 50 days ago — keep an eye on whether activity resumes.
What license does AutoGen use?
AutoGen ships under CC-BY-4.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AutoGen's commits signed?
100% of the last 100 commits to AutoGen 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 AutoGen?
HVTrust scores AutoGen 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.
