Open Source Mac Linters
Sort By:
Linters for Mac
View 1505 business solutionsBrowse free open source Linters and projects for Mac below. Use the toggles on the left to filter open source Linters by OS, license, language, programming language, and project status.
-
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
$300 Free Credits for Your Google Cloud ProjectsLaunch your next project with $300 in free Google Cloud credits—no strings attached. Test, build, and deploy without risk. Use your credits across the entire Google Cloud platform to find what works best for your needs. After your credits are used, continue with always-free tier services. Only pay when you're ready to scale. Sign up in minutes and start exploring.
-
1
golangci-lint
Fast linters Runner for Go
golangci-lint is a fast Go linters runner. It runs linters in parallel, uses caching, supports yaml config, has integrations with all major IDE and has dozens of linters included. ⚡ Very fast: runs linters in parallel, reuses Go build cache and caches analysis results. Yaml-based configuration. Integrations with VS Code, Sublime Text, GoLand, GNU Emacs, Vim, Atom, GitHub Actions. A lot of linters included, no need to install them. Minimum number of false positives because of tuned default settings. Nice output with colors, source code lines and marked identifiers. -
2
Ruff
An extremely fast Python linter, written in Rust
An extremely fast Python linter, written in Rust. Ruff aims to be orders of magnitude faster than alternative tools while integrating more functionality behind a single, common interface. Ruff can be used to replace Flake8 (plus dozens of plugins), isort, pydocstyle, yesqa, eradicate, pyupgrade, and autoflake, all while executing tens or hundreds of times faster than any individual tool. Ruff is extremely actively developed and used in major open-source projects. Ruff can be configured through a pyproject.toml, ruff.toml, or .ruff.toml file (see: Configuration, or Settings for a complete list of all configuration options). Ruff supports over 500 lint rules, many of which are inspired by popular tools like Flake8, isort, pyupgrade, and others. Regardless of the rule's origin, Ruff re-implements every rule in Rust as a first-party feature. -
3
Clj-kondo
A linter for Clojure code that sparks joy
A linter for Clojure code that sparks joy. Clj-kondo performs static analysis on Clojure, ClojureScript and EDN, without the need of a running REPL. It informs you about potential errors while you are typing. To detect lint errors across namespaces in your project, a cache is needed. To let clj-kondo know where to create one, make a .clj-kondo directory in the root of your project, meaning on the same level as your project.clj, deps.edn or build.boot. A cache will be created inside of it when you run clj-kondo. Before linting inside your editor, it is recommended to lint the entire classpath to teach clj-kondo about all the libraries you are using, including Clojure and/or ClojureScript itself. Since clj-kondo now knows about your version of ClojureScript via the cache, it detects that the number of arguments you passed to select keys is invalid. Each time you edit a file, the cache is incrementally updated, so clj-kondo is informed about new functions you just wrote. -
4
Dockle
Container Image Linter for Security
Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start. You can install dockle with the asdf version manager with this plugin, which automates the process of installing (and switching between) various versions of github release binaries. With asdf already installed, run commands to install dockle. You can scan your built image with Dockle in Travis CI/CircleCI. Though, you can ignore the specified target checkpoints by using .dockleignore file. Or, if you just want the results to display and not let the test fail for this, specify --exit-code to 0 in dockle command. -
Stop vibe-debugging.AppSignal's MCP server hands Claude, Cursor, or Zed your real errors, traces, and the deploy that shipped them. AI writes the fix; you review the diff.
-
5
commitlint
Lint commit messages
commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. We identify ease of adoption and developer experience as fields where there is room and need for improvement. The items on the roadmap should enhance commitlint regarding those aspects. -
6
go-critic
The most opinionated Go source code linter for code audit
The most opinionated Go source code linter. go-critic is a collection of checks that detect style, and performance issues as well as some common programming errors. We provide as many useful checks as possible. We’re prototyping and experimenting here. When specific check implementation is mature and proven useful, propose it’s integration into other linter. If a good checker can’t find a better home, it stays here. Almost 100 diagnostics that check for bugs, performance and style issues. Extensible without re-compilation with dynamic rules. Includes #opinionated checks with very strict and specific requirements. Self-documented: gocritic doc <checkname> gives a checker description. Usage of gocritic: gocritic [sub-command] [sub-command args...] Run gocritic without arguments to get help output. -
7
Ansible-lint
Best practices checker for Ansible
Ansible Lint is a command-line tool for linting playbooks, roles and collections aimed towards any Ansible users. Its main goal is to promote proven practices, patterns and behaviors while avoiding common pitfalls that can easily lead to bugs or make code harder to maintain. Ansible lint is also supposed to help users upgrade their code to work with newer versions of Ansible. Due to this reason we recommend using it with the newest version of Ansible, even if the version used in production may be older. As any other linter, it is opinionated. Still, its rules are the result of community contributions and they can always be disabled based individually or by category by each user. ansible-lint checks playbooks for practices and behavior that could potentially be improved. As a community-backed project ansible-lint supports only the last two major versions of Ansible. -
8
Optic
Generate, Diff, and Test OpenAPI Descriptions
Vizualize API changes to improve the quality of reviews. Test API changes to ensure nothing bad slips through. OpenAPI diffs are difficult to read. Because these files contain references, small changes can have a large effect on your API. Linters can not check for backward compatibility or enforce versioning and deprecation policies. Optic adds a visual changelog to every Pull Request that makes it easy to see exactly what API changes have been proposed. Optic tests each set of API changes in CI, making it more powerful than a linter. Our built-in checks will help any team ship a more reliable API. OpenAPI diffs are very difficult to review, comprehend and give feedback on. Optic’s changelogs are easy to understand allowing anyone (even non-developers) to participate in review. Optic goes beyond linting OpenAPI, it lets you write test about each set of API changes. We also make it easy to share your API standards. -
9
gts
TypeScript style guide, formatter, and linter
gts is Google's TypeScript style guide, and the configuration for our formatter, linter, and automatic code fixer. No lint rules to edit, no configuration to update, no more bike shedding over syntax. No configuration. The easiest way to enforce consistent style in your project. Just drop it in. Automatically format code. Just run gts fix and say goodbye to messy or inconsistent code. Catch style issues & programmer errors early. Save precious code review time by eliminating back-and-forth between reviewer & contributor. Opinionated, but not to a fault. We recommend you use the default configuration, but if you need to customize compiler or linter config, you can. Under the covers, we use eslint to enforce the style guide and provide automated fixes, and prettier to re-format code. -
Secure File Transfer for Windows with Cerberus by RedwoodCerberus supports unlimited users and connections on a single IP, with built-in encryption, 2FA, and a browser-based web client — all deployable in under 15 minutes with a 25-day free trial.
-
10
ktlint
An anti-bikeshedding Kotlin linter with built-in formatter
No configuration, which means no decisions to make, nothing to argue about and no special files to manage. While this might sound extreme, keep in mind that ktlint tries to capture (reflect) official code style from kotlinlang.org and Android Kotlin Style Guide (+ we respect your .editorconfig and support additional ruleset|s). Built-in formatter. So that you wouldn't have to fix all style violations by hand. Customizable output. plain (+ plain?group_by_file), JSON, HTML and check style reporters are available out-of-the-box. It's also easy to create your own. A single executable jar with all dependencies included. ktlint is a single binary with both linter & formatter included. All you need is to drop it in (no need to get overwhelmed while choosing among dozens of code style options). -
11
ESLint
The pluggable linting utility for identifying patterns in Javascript
ESLint is an open source tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. ESLint is written using Node.js -
12
tslint-to-eslint-config
Converts your TSLint configuration to the closest possible ESLint
Converts your TSLint configuration to the closest reasonable ESLint equivalent. The tslint-to-eslint-config command reads in any existing linter, TypeScript, and package configuration files, then creates an .eslintrc.js result based on them. For any TSLint rules with corresponding ESLint equivalents, those equivalents will be used in the new configuration. TSLint rules without ESLint equivalents will be wrapped with eslint-plugin-tslint. If passed without arguments, respects the excludes, files, and includes in your TypeScript configuration. -
13
lint-staged
Run linters on git staged files
Run linters against staged git files and don't let anything slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the 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 shell tasks with a list of staged files as an argument, filtered by a specified glob pattern. Linter commands work on a subset of all staged files, defined by a glob pattern. lint-staged uses micromatch for matching files. The concept of lint-staged is to run configured linter tasks (or other tasks) on files that are staged in git. lint-staged will always pass a list of all staged files to the task, and ignoring any files should be configured in the task itself. -
14
Angular ESLint
Monorepo for all the tooling related to using ESLint with Angular
Monorepo for all the tooling which enables ESLint to lint Angular projects. Follow the latest Getting Started guide on angular.io in order to install the Angular CLI. Create a new Angular CLI workspace in the normal way, optionally using any of the supported command line arguments and following the interactive prompts. As well as installing all relevant dependencies, the ng add command will automatically detect that you have a workspace with a single project in it, which does not have a linter configured yet. It can therefore go ahead and wire everything up for you! -
15
Joker
Small Clojure interpreter, linter and formatter
Joker is a small interpreted dialect of Clojure written in Go. It is also a Clojure(Script) linter. Send HTTP requests, read and parse JSON, work with file system, start external processes etc. Checks for syntax errors, function arity mismatches, unresolvable symbols, unused namespaces, vars, bindings and much more. Joker uses .joke filename extension. Normally exits after executing the script, unless --exit-to-repl is specified before --file <filename> in which case drops into the REPL after the script is (successfully) executed. (Note use of --file, in this case, to ensure <filename> is not treated as a <socket> specification for the reply.) Our goal is to be suitable for scripting (lightweight, fast startup). This is something that Clojure is not good at and my personal itch I am trying to scratch. Also, to provide some tooling for Clojure and its dialects. Joker has linter mode which can be used for linting Joker, Clojure and ClojureScript code. -
16
Jsonnet
Jsonnet, the data templating language
A data templating language for app and tool developers. Eliminate duplication with object-orientation or use functions. Integrate with existing / custom applications. Generate JSON, YAML, INI, and other formats. The name Jsonnet is a portmanteau of JSON and sonnet, pronounced "jay sonnet". It began life early 2014 as a 20% project and was launched on Aug 6. The design is influenced by several configuration languages internal to Google, and embodies years of experience configuring some of the world's most complex IT systems. Jsonnet is now used by many companies and projects. Jsonnet is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google. Jsonnet is open source (Apache 2.0), familiar syntax, reformatter, linter, editor & IDE integrations, and formally specified. -
17
SublimeLinter-eslint
This linter plugin for SublimeLinter provides an interface to ESLint
This linter plugin for SublimeLinter provides an interface to ESLint. It will be used with "JavaScript" files, but since eslint is pluggable, it can actually lint a variety of other files as well. SublimeLinter will detect some installed local plugins, and thus it should work automatically for e.g. .vue or .ts files. If it works on the command line, there is a chance it works in Sublime without further ado. Make sure the plugins are installed locally colocated to eslint itself. T.i., technically, both eslint and its plugins are described in the very same package.json. Configuration of the plugins is out-of-scope of this README. Be sure to read their README's as well. (If you just installed a plugin, without proper configuration, eslint will probably show error messages or wrong lint results, and SublimeLinter will just pass them to you.) -
18
eslint-config
Anthony's ESLint config presets
Anthony's ESLint config presets. Auto fix for formatting (aimed to be used standalone without Prettier). Designed to work with TypeScript, Vue out-of-box. Lint also for json, yaml, markdown. Sorted imports, dangling commas for cleaner commit diff. Reasonable defaults, best practices, only one-line of config. -
19
eslint-plugin-unicorn
More than 100 powerful ESLint rules
More than 100 powerful ESLint rules. You might want to check out XO, which includes this plugin. Each rule has emojis denoting if it belongs to the recommended configuration if some problems reported by the rule are automatically fixable by the --fix command line option, or if some problems reported by the rule are manually fixable by editor suggestions. Use a preset config or configure each rules in package.json. -
20
stylelint
A linter that helps you avoid errors and enforce conventions
stylelint understands the latest CSS syntax including custom properties and level 4 selectors. Extracts embedded styles from HTML, markdown and CSS-in-JS object & template literals. Parses CSS-like syntaxes like SCSS, Sass, Less and SugarSS. Has over 170 built-in rules to catch errors, apply limits and enforce stylistic conventions. Supports plugins so you can create your own rules or make use of plugins written by the community. Automatically fixes the majority of stylistic violations. Itis well tested with over 15000 unit tests. Supports shareable configs that you can extend or create. It is unopinionated so that you can customize it to your exact needs. stylelint has a growing community and is used by Facebook, GitHub and WordPress. You can configure the built-in stylistic rules to allow both multi-line and single-line rules. The choice of when to use each belongs to the user. -
21
Haskell Dockerfile Linter
Dockerfile linter, validate inline bash, written in Haskell
A smarter Dockerfile linter that helps you build best practice Docker images. The linter parses the Dockerfile into an AST and performs rules on top of the AST. It stands on the shoulders of ShellCheck to lint the Bash code inside RUN instructions. You can run hadolint locally to lint your Dockerfile. You can download prebuilt binaries for OSX, Windows and Linux from the latest release page. However, if this does not work for you, please fall back to container (Docker), brew or source installation. Configuration files can be used globally or per project. -
22
JavaScript Standard Style
JavaScript style guide, linter, and formatter
JavaScript Standard Style is a JavaScript style guide with linter and automatic formatter. It’s the simple, easy, fuss-free way to get a consistent style in your project. No more hundred-line style configuration files for every module/project; no more messy or inconsistent code; and no more wasting time sending code back and forth between reviewer and contributor. With Standard, your code is automatically formatted, no configuration necessary. With Standard, code clarity and community conventions is paramount. This may not make sense to all projects or development cultures, but does make a lot of sense for open source projects where setting up clear, automated contributor expectations makes a project healthier. -
23
Ruff Visual Studio Code
A Visual Studio Code extension with support for the Ruff linter
Ruff Visual Studio Code is an official Visual Studio Code extension that integrates the Ruff Python linter and formatter directly into the development environment, enabling developers to maintain high code quality with minimal configuration. It provides real-time linting and formatting feedback as developers write code, helping catch errors, enforce style guidelines, and automatically fix issues where possible. The extension is built on top of Ruff’s high-performance Rust-based engine, which is significantly faster than traditional Python linting tools, allowing near-instant feedback even on large codebases. It supports both linting and formatting workflows, consolidating the functionality of multiple tools such as Flake8, Black, and isort into a single unified interface. -
24
Ultracite
A highly opinionated, zero-configuration linter and formatter
Ultracite is a highly opinionated, zero-configuration linting and formatting preset designed primarily for modern JavaScript/TypeScript codebases. It is built on top of the Biome toolchain (written in Rust) and aims to deliver sub-second performance so that formatting and linting feel seamless, even on large projects. Because it comes pre-configured with sensible defaults for frameworks like React and Next.js, developers can adopt it with minimal setup—simply run npx ultracite init and start coding. The project emphasizes type-safety and best practices, enforcing stricter rules out of the box so that unsafe or sloppy patterns are discouraged. It also positions itself as “AI-ready,” meaning it’s designed to integrate smoothly into workflows where AI code generation (e.g., from Copilot, Claude Code, etc) is involved, ensuring consistent style across team-written and machine-written code. -
25
wemake-python-styleguide
The strictest and most opinionated python linter ever!
Welcome to the strictest and most opinionated Python linter ever. wemake-python-styleguide is actually a flake8 plugin with some other plugins as dependencies. Ensures consistency - no matter who works on it, the end product will always be the same dependable code. Helps avoid potential bugs - strict rules make sure that you don't make common mistakes. Efficient code reviews - each piece of code has a similar familiar style and syntax. If it passes all the checks, there's little left to review! Fewer code revisions - strict linting ensures that you don't have to re-write the codebase again and again. Reduce code redundancy - Sometimes we write complex code as we are thinking in a certain way about a problem. The linter offers suggestions that can help simplify the code and eliminate redundant statements. The ultimate goal of this project is to make all people write exactly the same Python code.