Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI security professionals today have built penetration testing workflows that require stitching together a custom backend (Go or Python or Rust) + a hand-wired Neo4j Knowledge Graph (or a hand-written SQLite layer) + a hand-rolled observability stack (Grafana + Prometheus + Jaeger + Loki) + a hand-curated LLM provider interface (per-provider credential handling + retry logic + per-provider co
Who should use it
Who should skip it
Skip vxcontrol/pentagi if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
vxcontrol/pentagi is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. vxcontrol/pentagi leads on workflow potential (9.4) and momentum (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned vxcontrol/pentagi a composite score of 8.7 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 19; 047* repo is at production-grade active maintenance (created 2025-01-06; MIT verified on 2026-07-09) but the consumer SHOULD note that PentAGI is an *offensive* security agent by design -- any deployment must operate within explicit user-controlled scope and authorization; the consumer SHOULD configure PentAGI to operate only on user-authorized targets (this is the user's compliance obligation -- not PentAGI's enforcement).