6 projects tagged "code quality"
SCC is a cross-platform tool that counts the number of lines in source code files. It features a GUI that gives the user complete control over which files are processed. Blank lines are counted separately from lines containing source code statements. Configurable regular expressions can be applied to count parts of source code files separately. Regular expressions are applied according to a file type rather than to all files. It can process any textual source code file, includingJava, C/C++/C#, Perl, Python, PHP, Ruby, and TCL. The line count is split between blank, counted, and remaining lines. Results and summaries can be exported to a CSV file for further processing.
The Neptuner codebase management tool suite includes programs for: code browsing, review, complexity analysis, and code reformatting. Share your codebase easily as browse-packs. UBoat Browse-Packs allow others to browse through, comment on, and review your code with just a Web browser.
UBoat Code Navigator allows you to browse through and do manual reviews of your source code with just a Web browser. It works completely offline; there is no server or configuration required. UBoat Browse-Packs enable everybody to browse through, comment on, and review your code without any IDE, platform, or build dependencies. It lets you share your codebase with ease and also view code complexity metrics like LoC and nesting.
Quality-Check provides a small Java library for basic runtime code quality checks. It provides similar features to org.springframework.util.Assert or com.google.common.base.Preconditions without the need to include big libraries or frameworks such as Spring or Guava. The package Quality-Check tries to replace these libraries and provide all the basic code quality checks. These basic code checks avoid technical errors using a fail-early approach, by checking each input parameter to a public method to be technically valid.
CODERU is a Java code quality tool to enforce good design in respect to package dependencies. Its rules rely on reserved package names, and the allowed dependency rules between them are expressed in a general way. Unlike other tools that force you to define allowed or disallowed individual package dependencies, CODERU is based on a fixed set of general rules. The dependencies between packages need not be defined explicitly. These general dependency rules are based on common design practices which are reflected in preserved package names: "api", "common", "impl", and "factory". It includes a tool for checking your code for rule conformance.