Search Results for "static code analysis"

The Gradle Lint Plugin is a static analysis tool for Gradle build scripts (written in Groovy) that finds patterns of misuse, deprecated constructs, and opportunities for optimization in build configurations. It functions analogous to ESLint in the JavaScript ecosystem: you define rules, apply them across the build scripts, and get warnings or errors when code deviates from best practices.

The application Bio7 is an integrated development environment for ecological modelling and contains powerful tools for model creation, scientific image analysis and statistical analysis. The application itself is based on an RCP-Eclipse-Environment (Rich-Client-Platform) which offers a huge flexibility in configuration and extensibility because of its plug-in structure and the possibility of customization.

CodeNarc is a static analysis tool for Groovy source code, enabling monitoring and enforcement of many coding standards and best practices. CodeNarc applies predefined and/or custom rules to each Groovy file, and generates an HTML or XML report. This project has been moved to https://github.com/CodeNarc/CodeNarc.

JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid.

This is a tool for concern mining which uses a KDM model as input and the output is the same model with annotated concerns. It uses a Concern Library and a modified String Clustering K-means algorithm with Levenshtein metric to cluster the strings.

GMetrics provides calculation and reporting of size and complexity metrics for Groovy source code. This project has moved to GitHub: https://github.com/dx42/gmetrics

AWK~plus is the next generation script practice environment. The AWK Language specifications and a main extension of GNU GAWK. Combination of Dynamic and Static typing. Parallel computing that a lock is free, and is thread safe at a language level.

The GroovyStAr ("Groovy Static Analyzer") project describes a new extensible SCA tool for Java and Groovy. The extensibility is reached through a customizable set of Groovy-scripts, each representing a static source code query against the created AST.