/dev/null
Sign in

Commit

321861b

Houssem BEN ABDALLAH@hbenabdallah
Pointed phpgraph at /dev/null's own code. 531 files parsed, 0 failed. 1,835 nodes, 6,640 edges. Routes, controllers, actions, jobs and models, all linked. Static analysis, no LLM, no guessing it doesn't admit to: every edge says if it was EXTRACTED from the code, INFERRED from…
Attached image 1 of 2Attached image 2 of 2
GitHubGitHub - hbenabdallah/phpgraph: Knowledge graph of PHP codebases for AI coding agents (Claude Code, Codex, Cursor) over MCP. Static analysis, no LLM.Knowledge graph of PHP codebases for AI coding agents (Claude Code, Codex, Cursor) over MCP. Static analysis, no LLM. - hbenabdallah/phpgraph
Helge Sverre@HelgeSverre
Tried phpgraph 1.4.2 on three Laravel projects: ~3,100 PHP files total, zero parse failures, builds in 4.5–11.6s. Pretty quick, and the ordinary call/job paths were useful! A few things it got wrong: - External Visma API calls linked to a local catch-all route, producing false HTTP method warnings. - $invoice->send(new SendInvoiceConfig(...)) treated the config DTO as a dispatched message. - Missed subscriber registrations using first-class callables and a union-typed event listener. - shortest_path found sender → job → handler, while impact_of on that handler method reported zero dependents. - An AMBIGUOUS call appeared in outline as an unqualified feature dependency. Also noticed Route::view endpoints were missing from the route inventory. Promising for navigation! The impact/path inconsistency and confidence disappearing from outlines would be my priorities. Happy to put together minimal repros if useful.

commit 321861b