September 2026 Summaries
2 posts from Sonar
Filter
Month:
Year:
Post Summaries
Back to Blog
SonarQube Cloud now natively supports MuleSoft DataWeave, Gosu, Groovy, and PowerShell, extending its deterministic code analysis across more than 40 languages without requiring plugins or manual setup. Available for repositories on GitHub, GitLab, Bitbucket, and Azure DevOps, the added support evaluates bugs, security vulnerabilities, and maintainability issues through the same dashboards and pull-request checks used for other languages. The expansion targets business-critical areas that have often lacked consistent verification, including enterprise integration flows written in DataWeave, insurance and claims systems built with Gosu, Jenkins and Gradle pipeline automation in Groovy, and infrastructure provisioning and operations scripts in PowerShell. SonarQube Cloud emphasizes that both AI-generated and developer-written code require independent validation, offering issue explanations and remediation guidance to help teams identify defects, security risks, and technical debt before production.
Sep 04, 2026
1,266 words in the original blog post.
Sonar Vortex is presented as an enterprise harness for AI coding agents that uses SemSitter, an in-house semantic navigation engine, to replace grep-and-file-reading workflows with queries over a continuously updated Unified Dependency Graph of code, documentation, and cross-language relationships. The text argues that conventional agent navigation creates substantial cumulative costs because every file read remains in the conversation and is repeatedly billed on later model turns; in one approximately 800-line pull request, this reportedly produced 156 million billed context tokens, a peak context window of about 459,000 tokens, and an estimated $41 session cost, while 18 comparable pull requests averaged roughly 234 million tokens and $65 each. Using a call-site-resolution refactor as an example, it contrasts broad regex searches and whole-file reads with graph lookups that can identify a method’s owning type, definition, return value, callers, relevant documentation, and corresponding implementations in other languages. The proposed approach is intended to reduce persistent context, lower navigation-related spending, and improve correctness by finding semantic dependencies that text search may miss, particularly in repositories larger than an agent’s context window.
Sep 01, 2026
2,155 words in the original blog post.