Blog
Customer source code gets expensive the moment you keep it
Semfora deletes your repository clone after every analysis run, including failed ones. What a code analysis tool actually needs to store, and what that deletion costs to engineer.
One missing return statement, three years on main
A goroutine in Gitea was able to busy-spin a CPU core for three years, and nobody ever filed it. What a deterministic scan found in Gitea, VS Code, Excalidraw, and cal.com, and where the five upstream PRs stand.
Good bones, drowning in copy-paste: Semfora vs. fifteen-year-old WebForms
I pointed the Semfora engine at the oldest, ugliest C# I could find: nopCommerce, December 2010. WebForms, SOAP proxies, Visual SourceSafe bindings. It indexed 22,585 symbols in 40 seconds with zero errors, then named exactly where the bodies were buried.
Measuring what AI is doing to your code
AI assistants ship code faster than any team can review it. Here is how we turn "the AI wrote a lot this sprint" into a number you can actually govern.
Introducing Semfora: a structural map of your codebase, rebuilt on every merge
Your dashboard, your AI chat, and your PR gate should all read the same map of your code. Here is why we built one, and what it measures.