Deptrac β static code analysis tool for PHP projects
https://fed.brid.gy/r/https://www.linuxlinks.com/deptrac-static-code-analysis-tool/
Deptrac β static code analysis tool for PHP projects
https://fed.brid.gy/r/https://www.linuxlinks.com/deptrac-static-code-analysis-tool/
PHPArkitect β define architectural rules as executable PHP code
Opengrep -open-source static code analysis (SAST) engine- v1.23.0 released
Opengrep is an open-source static code analysis (SAST) engine - a community-driven alternative to Semgrep, born after Semgrep moved critical scanning features behind a commercial license. It supports inter-procedural and cross-file analysis, SARIF/JSON output, and is backed by a consortium of 10+ appsec organizations. Version v1.23.0 is out with Crystal language support and several bug fixes.
Static code analysis can't fix your code, but it can tell your AI tooling where the risk hides.
I'm still trying to figure out what other are seeing, and this post is kind of a step back and trying to figure out. Maybe I was missing the bigger picture, so quality gates here we come.
https://jeferson.me/blog/2026/06/12/code-quality
#AI #Automation #Blog #CD #CI #CodeQuality #DevOps #QualityGates #SoftwareEngineering #StaticAnalysis #TechnicalDebt
Applicatives allow performing static analysis, while monads do not. But what does it mean in practice? Why is it so? And what kind of static analysis is this referring to? And what happens if we use categories instead of monads?
These are some of the questions Iβm trying to provide an answer to in my latest blog post:
https://marcosh.github.io/post/2026/05/21/homomorphic-static-analysis.html
Rust's compile-time guarantees are deliberately incomplete - the compiler catches most issues, but not all. What's left behind is the question.
At Oxidize 2026, Rolland Dudemaine (TrustInSoft) shares findings from analysing production Rust code: what bugs survive, and when additional tooling is worth it.
π https://oxidizeconf.com/sessions/whats_left_to_find_in_rust
#Oxidize2026 #RustLang #FormalVerification #StaticAnalysis #CodeQuality
Question related to my previous post: is it possible to do some kind of static analysis on categorical code?
Or, what constraints should be imposed (or removed) on a category so that its code supports static analysis?
Recently, I made a stupid mistake that made me think about the way C++ APIs handle dependencies and what we can do to prevent dangling references and lifetime issues. π€
It was a surprisingly fun topic to explore that led me to the discovery of a very cool static analysis tool. Can you guess which one? π
You can find out in the article I wrote about the topic here:
β€ https://medium.com/@nerudaj/type-safe-dependency-management-in-c-a293703f00ff