Frappe Inspector - Static analysis for Frappe and ERPNext projects

Hey Product Hunt 👋 I built Frappe Inspector after repeatedly running into the same limitation while working with Frappe and ERPNext projects. Editors understand Python, JavaScript and JSON individually, but they usually do not understand the conventions connecting a DocType schema to its controller, client script, hooks, patches, fixtures, Custom Fields and related DocTypes. Frappe Inspector builds that missing project model locally. The free Community edition includes: • Frappe bench and app discovery • DocType and field exploration • Related-file navigation • Frappe-aware completion and definitions • Conservative diagnostics • DocType relationship graphs • Local project scans and Markdown reports Universal Pro adds deeper project-wide inference, Git-based migration comparisons, Custom Field and Property Setter analysis, JSON/SARIF reports, advanced MCP tools and GitHub Action features. Project files are analyzed locally as text. Frappe Inspector does not execute project code, run Bench, connect to Frappe sites or upload source code during normal analysis. It is available for VS Code, Cursor, JetBrains IDEs, CLI, MCP-compatible AI clients and GitHub Actions. Universal Pro covers VS Code, Cursor, CLI, MCP and GitHub Actions; JetBrains Marketplace licensing is separate. I would particularly appreciate feedback about: 1. False positives and unsupported Frappe patterns 2. Performance on larger benches 3. Migration problems that should be detected earlier 4. Features that would genuinely save time in everyday Frappe development Thanks for checking it out. Blunt and technical feedback is very welcome.