- Always FREE
The smart integration with Git, helps to reconstruct when and who wrote the lines of code of the current code quality issues.
You can catch which are exactly the new issues produced in your code before starting a pull request or committing your repository.
Detect which are the patches that you can apply to fix your coding style issues.
You can compose which is the ruleset you need by combining rulesets from different providers (e.g PMD, FindBugs, CheckStyle)
Prioritize the files to fix, to improve your productivity with the features that now matter.
WalkModHub analyzes your Git repository with existing open source technologies to detect code quality issues and offers, for some of the most common issues, quick fixes that can be integrated by means of a patch.
Moreover, you can safely add to your existing open source static code analysis tool, incremental checking capabilities. Therefore, you can automatically fix and prevent new code quality issues.
Try it now in your own machine with Docker Compose, running the following commands:
wget -O docker-compose.yml http://tinyurl.com/h5up3zl docker-compose up
It depends on which are the most critical code quality issues for you. However, considering open source projects with different rulesets, you can improve between a 6-20% only by applying the generated quick fixes.
Yes. We support static code analysis tools that can be run as part of your build or as a new task in your continuous integration (e.g Jenkins) pipeline. Our plugins connect to walkmodhub to resolve which are the introduced new issues.
Currently, WalkmModHub integrate PMD, which supports multiple programming languages, and WalkMod. Actively, we are adding more static code analysis tools.
Git contains all the history of our project, and the last file touched are those which contain the new features that currently matters. If we focus on fixing the issues that affect on those new files, we will achieve a short term productivity benefits.
We apply any existing rule of the supported static code tools for the detected languages of the project. Afterwards, the user can customize which rulesets are no longer applied or which issues can be ignored.
Yes, since we use WalkMod to apply quick fixes and it is open source. Any approved update on the technology is automatically applied in WalkModHub without any extra configuration.
Everything started in Barcelona, when two college friends, passionate about software engineering, discussed about automatic ways to generate and fix software. As a result, we created WalkMod, an open source framework to design code transformations. However, with the help of the open source community, and specially of MetricStream and Shibsted, we realized that WalkMod was too generic while developers were specifically interested in fixing issues reported by static code analysis tools.
However, WalkMod applies code transformations across the whole code base, which raises issues specially when the codebase is old and large. For this reason, we develop WalkModHub, in order to assist developers in the process of fixing coding style issues on legacy code. This is something that other similar products are not considering as these are mainly focused on just controlling upcoming issues. Fixing existing issues, reduces the time effort to understand and maintain existing code. How many times have you fixed a coding style issue (e.g code inside comments) on legacy code over and over again?
You can find our talks about how to add fixings on your development workflow on blogs, social platforms, and conferences.