Is AutoGen safe?
AutoGen scores 74.9/100 (Grade B), ranked #60 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
OSSF Scorecard rates its supply-chain practices 5.7/10;
100% of recent commits are signed;
last pushed 2026-04-15. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
74.9/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Maintenance
6.2/20
What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signalsThe repo was last pushed 87 days ago. Fresh activity helps separate stable projects from stale ones.
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. 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 refreshed2026-07-11 04:00 UTC·Repo last pushed 87 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
59.6k
Forks
9.0k
Last Push
2026-04-15
87 days ago
Commits (4 wk)
0
Downloads (7d)
306,076
pypi
HN mentions (30d)
2
Open Issues
555
Rank Change
=
was #60
Analysis
HVTrust Dimensions
74.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.6 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.3 / 17
MaintenanceFreshness and commits
6.2 / 20
AdoptionStars and downloads
18.8 / 20
Activity Inputs
60.2 / 100
StarsRepository reach
28.7 / 30
FreshnessLast push recency
12.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
18.4 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.7 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
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
Maintained0
Packaging10
Pinned-Dependencies0
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is AutoGen safe?
AutoGen 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 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.7/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 87 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.
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
high confidence
Implemented
AutoGen appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
browser
code
database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 AutoGen'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.
Runtime surface grew — new detected provider dependencies: OpenAI, Redis
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-05-24
Provenance Added
Package provenance attestation detected
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.
