Repowise · Codebase intelligence
jzacharie / pylos
Enterprise-grade Rust LLM Gateway & MCP Proxy. A high-performance, ultra-low latency AI proxy with built-in governance, cost control, semantic caching, vector memory, guardrails, and a React admin dashboard.
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 6 (30%) actually needed a bug fix in the last 6 months — 3.5× better than picking files at random.
Languages
- rust38.5%
- typescript17.3%
- sql14.0%
- markdown9.4%
- yaml7.9%
- json3.2%
- toml2.5%
Key modules5
- sql
pylos-application
crates/pylos-application
- rust
pylos-core
crates/pylos-core
- rust
pylos-infrastructure
crates/pylos-infrastructure
- rust
pylos-server
crates/pylos-server
ui
How jzacharie/pylos works
Enterprise-grade Rust LLM Gateway & MCP Proxy. A high-performance, ultra-low latency AI proxy with built-in governance, cost control, semantic caching, vector memory, guardrails, and a React admin dashboard. This page is an auto-generated, always-fresh map of the jzacharie/pylos repository, written primarily in Rust. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 278 source files, 3,129 symbols, and 12 languages, structured as a monorepo with 5 packages. Git churn analysis flags 28 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 134 tightly-coupled module communities.
Use the panels above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.