Displaying 1 to 20 from 107 results

linter - A Base Linter with Cow Powers http://steelbrain.me/linter/

Linter is a base linter provider for the hackable Atom Editor. Additionally, you need to install a specific linter for your language. You will find a full list on atomlinter.github.io.It provides a top-level API to its consumer so that they can visualize errors and other types of messages with ease.

alex - Catch insensitive, inconsiderate writing

📝 alex — Catch insensitive, inconsiderate writing.Whether your own or someone else’s writing, alex helps you find gender favouring, polarising, race related, religion inconsiderate, or other unequal phrasing in text.

gometalinter - Concurrently run Go lint tools and normalise their output

The number of tools for statically checking Go source for errors and warnings is impressive.eg.

go-tools - A collection of tools and libraries for working with Go code, including linters and static analysis

honnef.co/go/tools/... is a collection of tools and libraries for working with Go code, including linters and static analysis.These tools are supported by patrons on Patreon and sponsors. If you use these tools at your company, consider purchasing commercial support.

goreporter - A Golang tool that does static analysis, unit testing, code review and generate code quality report

Install goreporter (see above).You have to confirm that your project is operational. In particular, the problem with vendor, when the package is not found in the default path, goreporter will look again from the possible vendor path.

lint-staged - 🚫💩 — Run linters on git staged files

Linting makes more sense when running before committing your code. By doing that you can ensure no errors are going into repository and enforce code style. But running a lint process on a whole project is slow and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary npm and shell tasks with a list of staged files as an argument, filtered by a specified glob pattern.

credo - A static code analysis tool for the Elixir language with a focus on code consistency and teaching

Credo is a static code analysis tool for the Elixir language with a focus on teaching and code consistency. It implements its own style guide.

awesome-static-analysis - A curated list of static analysis tools, linters and code quality checkers for various programming languages

This is a collection of static analysis tools and code quality checkers. Pull requests are very welcome! Note: ©️ stands for proprietary software. All other tools are Open Source. To the extent possible under law, Matthias Endler has waived all copyright and related or neighboring rights to this work. Title image Designed by Freepik.

interfacer - A linter that suggests interface types

A linter that suggests interface types. In other words, it warns about the usage of types that are more specific than necessary.This tool inspects the parameters of your functions to see if they fit an interface type that is less specific than the current type.

SpotBugs - FindBugs' successor, A tool for static analysis to look for bugs in Java code.

SpotBugs is the spiritual successor of FindBugs, carrying on from the point where it left off with support of its community. SpotBugs is a program which uses static analysis to look for bugs in Java code.

postcss-bem-linter - A BEM linter for postcss

A PostCSS plugin to lint BEM-style CSS.BEM-style describes CSS that follows a more-or-less strict set of conventions determining what selectors can be used. Typically, these conventions require that classes begin with the name of the component (or "block") that contains them, and that all characters after the component name follow a specified pattern. Original BEM methodology refers to "blocks", "elements", and "modifiers"; SUIT refers to "components", "descendants", and "modifiers". You might have your own terms for similar concepts.

linter - Static Analysis Compiler Plugin for Scala

Linter is a Scala static analysis compiler plugin which adds compile-time checks for various possible bugs, inefficiencies, and style problems. Please help support the development of Linter.

phpqa - PHPQA all-in-one Analyzer CLI tool

This project aims to serve as a CLI tool to make easy the use of different PHP tools related to Quality Assurance and code analysis in PHP. Every analyzer tool handles arguments and options using different formats, the goal of this project is to provide a single way to interact with those projects, you can also set options and arguments using a default configuration file when the project supports it.

esprint - Fast eslint runner

esprint (pronounced E-S-sprint) speeds up eslint by running the linting engine across multiple threads. esprint sets up a server daemon to cache the lint status of each file in memory. It uses a watcher to determine when files change, to only lint files as necessary. It also has a CI mode where it does not set up a daemon and just lints in parallel. esprint will find the root of your project automatically and lint the whole project. In default mode, esprint will start a background server to watch source files and cache lint results in memory.

polyjuice - A utility to convert JSHint and JSCS files into ESLint files and vice-versa

Polyjuice is a utility that converts JSHint and JSCS files into ESLint files and the other way around. When using polyjuice.from.eslint an object with keys jscs and jshint is returned.