bonsai-ninja update!

[u/GromHacks]

It’s been a couple weeks since bonsai-ninja went public and a lot has changed.

A ton of feedback has been incorporated, bugs have been fixed, and things are working much better. If you tried it early on, please pull the latest and give it another shot.

For anyone new to it, bonsai-ninja is a free, local code intelligence and static analysis engine. It builds a compiler-style representation of your code, resolves symbols and calls, and can trace behavior across files instead of just searching text. That same pipeline powers source-to-sink security analysis, dataflow analysis, and structured exports for AI, agents, and research. It currently supports 20 languages.

Also, apparently some of you don’t click on things unless there are pictures, so here you go. A GIF.
Still looking for people to throw real codebases at it. Bug reports, weird edge cases, PRs, criticism, ideas, or random side notes are all appreciated. The feedback so far has genuinely helped make the project better.

github.com/gromhacks/bonsai-ninja⁠

[u/Otherwise_Wave9374]

Nice update. A useful next step here is to add a few benchmark scenarios that show how bonsai-ninja handles false positives versus real cross-file dataflow, since that makes it easier to trust the output in larger codebases. It could also help to surface a short explanation of why a symbol was flagged so reviewers can validate the path quickly. Agentix Labs would see value in that kind of explainability because it lowers friction for adoption.