Open Source Linux Code Review Software - Page 5
Sort By:
Code Review Software for Linux
View 14 business solutions-
Demo Series - Small Business Backup By VeeamWatch this on-demand demo series and learn how to protect your Microsoft 365 data with clear, simple, actionable steps that are easy to implement for businesses of all sizes.
-
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
1
cargo-crev
A cryptographically verifiable code review system for the cargo
A cryptographically verifiable code review system for the cargo (Rust) package manager. cargo-crev is an implementation of Crev as a command-line tool integrated with cargo. This tool helps Rust users evaluate the quality and trustworthiness of their package dependencies. Crev is a language and ecosystem agnostic, distributed code review system. Use reviews produced by other users. Increase the trustworthiness of your own code. Build a web of trust of other reputable users to help verify the code you use. Static binaries are available from the releases page. Crev is a system for verifying the security and reliability of dependencies based on collaborative code reviews. Crev users review the source code of packages/libraries/crates and share their findings with others. Crev then uses Web of Trust to select trusted reviews and judge the reputation of projects' dependencies. -
2
Chex4j allows you to document and enforce @pre and @post conditions of method calls with runtime or build time class file instrumentation. Conditions run as fast as normal code.
-
3
diff-so-fancy
Make your diffs human readable instead of machine readable
diff-so-fancy strives to make your diffs human readable instead of machine readable. This helps improve code quality and helps you spot defects faster. diff-so-fancy is also available from NPM, Nix, brew, and as a package on Arch and Debian Linux. Windows users may need to install MinGW or the Windows subsystem for Linux. By default, the separator for the file header uses Unicode line-drawing characters. If this is causing output errors on your terminal, set this to false to use ASCII characters instead. By default, the separator for the file header spans the full width of the terminal. Use this setting to set the width of the file header manually. Pull requests are quite welcome, and should target the next branch. You can simplify git header chunks to a more human readable format. We are also looking for any feedback or ideas on how to make diff-so-fancy even fancier. -
4
eslint-plugin-compat
Check the browser compatibility of your code
Lint the browser compatibility of your code. Browser targets are configured using a browser list. You can configure browser targets in your package.json. If no configuration is found, browser list defaults to "> 0.5%, last 2 versions, Firefox ESR, not dead". Add polyfills to the settings section of your eslint config. Append the name of the object and the property if one exists. Toolchains for native platforms, like iOS and Android, have had API linting from the start. It's about time that the web had similar tooling. -
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
5
eslint-plugin-import
ESLint plugin with rules that help validate proper imports.
This plugin intends to support linting of ES2015+ (ES6+) import/export syntax, and prevent issues with misspelling of file paths and import names. All the goodness that the ES2015+ static module syntax intends to provide, is marked up in your editor. The maintainers of eslint-plugin-import and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open-source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. With the advent of module bundlers and the current state of modules and module syntax specs, it's not always obvious where import x from 'module' should look to find the file behind module. Up through v0.10ish, this plugin has directly used substack's resolve plugin, which implements Node's import behavior. This works pretty well in most cases. -
6
funcfinder
function finder
ff util is created for searching some text (functions, variables, definitions) in some source tree in all files (and just for fun), a program for programmers. -
7
Recognizes typical patterns in Java code which could be replaced with functions provided by open source libraries http://www.jnorm.org
-
8
jul-comments
JCS - JUL Comment System
JCS - JUL Comment System is a way of documenting your JavaScript source code while keeping the comments in a separate file. It allows you to associate the comments to any version of the source code and to get the updated commented code. Also, JCS is able to generate and to document the code for an entire JavaScript namespace or DOM tree loaded by a web page. System requirements / Download the desktop app OR: * a CSS2.1 compliant web browser with JavaScript 1.5 or later engine * Node.js 0.10.0 or later installed * OR a web server with PHP 5.2.0 or later extension * 1024x768 minimum resolution All major browsers supported, including: FF 4+, IE 8+, Edge, Safari 4+, Chrome 2+, Opera 10+., IOS 4+, Android 2.3+. -
9
luastyle
lua source code beautifier
Luastyle is source code beautifier for lua language. -
Go from Code to Production URL in SecondsSkip the Kubernetes configs. Cloud Run handles HTTPS, scaling, and infrastructure automatically. Two million requests free per month.
-
10
luzienseditor
LuziensEditor ist eine kleine IDE für Java, C/C++, und Webentwicklung
LuziensEditor ist eine kleine IDE für Java, C/C++, und Webentwicklung mit einigen Besonderheiten. - Direkter Zugriff auf XAMPP - Eigene Konsole - Syntax highligts - Eigene Versionsverwaltung - Programme als Debian Paket verpacken - ... -
11
misspell-fixer
Simple tool for fixing common misspellings, typos
Utility to fix common misspellings, typos in source codes. There are lots of typical misspellings in program codes. Typically they are more eye-catching in the living code but they can easily hide in comments, examples, samples, notes and documentations. With this utility you can fix a large number of them very quickly. Be aware that the utility does not check or fix file names. It can easily happen that a misspelled word is fixed in a file name in a program's code, but the file itself will not be renamed by this utility. And also important to note to be extra careful when fixing public APIs! A manual review is always needed to verify that nothing has been broken. -
12
nvim-regexplainer
Describe the regexp under the cursor
Describe the regular expression under the cursor. You need to install regex with nvim-treesitter, as well as the grammar for whichever host language you're using. -
13
pornsvn is a CLI tool for subversion. It provides a simple interface to review your changes and choose what files you want to commit, much like what tig is for git, albeit with less features (for now!). It is written in Perl with Curses::UI.
-
14
Reviewing memory allocation and data structures of an extant Sourceforge project unix-named "simupop". A new development version of the extant project is established and the ultimate goal is to "rev up" the old, hence the project name.
-
15
stats.js
JavaScript performance monitor
This class provides a simple info box that will help you monitor your code performance. FPS Frames rendered in the last second. The higher the number the better. MS Milliseconds needed to render a frame. The lower the number the better. MB MBytes of allocated memory. (Run Chrome with --enable-precise-memory-info). CUSTOM User-defined panel support. -
16
svncr, abbreviated "subversion code review tool" uses svn to give you a blame, log and diff all in one report. It is a diff format report that can get split out by filter that matches to log messages and code.
-
17
vscode-pull-request-github
GitHub Pull Requests for Visual Studio Code
This extension allows you to review and manage GitHub pull requests and issues in Visual Studio Code. The support includes authenticating and connecting VS Code to GitHub. GitHub Enterprise is supported by the community, please see this PR for how to set it up. Listing and browsing PRs from within VS Code. Reviewing PRs from within VS Code with in-editor commenting. Validating PRs from within VS Code with easy checkouts. Terminal integration that enables UI and CLIs to co-exist. Listing and browsing issues from within VS Code. Hover cards for "@" mentioned users and for issues. Completion suggestions for users and issues. A "Start working on issue" action which can create a branch for you. Code actions to create issues from "todo" comments. -
18
Removal tool for viruses source code, no problem if you want to combine or developed my code. Thank's
