Is agent-zero maintained?

GraphCanon rates agent-zero "Very active" (96% maintenance signal from public GitHub metadata, computed 1d). Last push was 2 days ago. 15 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is agent-zero safe to use?

Last scanned 1mo (deps profile). Status: 99 low - 99 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify agent-zero as safe - review maintenance, provenance, and scan findings on this page before adopting.

Is agent-zero a fork?

No. agent-zero is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does agent-zero have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 99 low - 99 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

How often is the agent-zero trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 1d (methodology github_public_v1).

What does GraphCanon never claim about agent-zero?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for agent-zero. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for agent-zero?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/agent-zero/Trust report

Trust and health report

agent-zero - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 1d · GitHub synced 1d

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 2d ago · last release 1w · 15 releases (90d)

+453 stars (30d) · -67 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 812975380
Not a fork
Verified publisher: organization account
Computed 1d

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings

Last query: 1mo
Scanner: osv@v1
Stored findings: 99

View source evidence

deps.dev advisories

Not queried

Scanner: deps.dev@v1

View source evidence

OpenSSF Scorecard

Not queried

Scanner: openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-7545-fcxq-7j24

GitPython@3.1.43 · osv@v1

requirements.txt

GHSA-mv93-w799-cj2w

GitPython@3.1.43 · osv@v1

requirements.txt

GHSA-rpm5-65cw-6hj4

GitPython@3.1.43 · osv@v1

requirements.txt

GHSA-v87r-6q3f-2j67

GitPython@3.1.43 · osv@v1

requirements.txt

GHSA-x2qx-6953-8485

GitPython@3.1.43 · osv@v1

requirements.txt

GHSA-44vg-5wv2-h2hg

simpleeval@1.0.3 · osv@v1

requirements.txt

PYSEC-2026-132

simpleeval@1.0.3 · osv@v1

requirements.txt

GHSA-2g6r-c272-w58r