dotenv-linter (Rust)

Linter for ABAP, written in TypeScript.

Enhances the SAP Code Inspector with new and customizable checks.

Static checker for GitHub Actions workflow files. Provides an online version.

Lint, analyze, normalize, transform, sandbox, run, step through, and visualize user JavaScript, in node or the browser.

Spell, style and grammar checker.

Catch insensitive, inconsiderate writing

Find inefficiently packed structs.

Inspects tar archives and tries to spot portability issues in regard to POSIX 2017 pax specification and common tar implementations. This project is intended to be used by maintainers of projects who want to offer portable source code archives for as many systems as possible. Checking tar archives with alquitran before publishing them should help spotting issues before they reach distributors and users.

A static code analysis tool for Crystal.

Discover, analyze, and certify container images. A service that analyzes Docker images and applies user-defined acceptance policies to allow automated container image validation and certification

Run static analysis on Android projects.

Combines lint errors of multiple projects into one output, check lint results of multiple sub-projects at once.

Platform agnostic binary analysis framework from UCSB.

Linter for Angular projects

Checks playbooks for practices and behaviour that could potentially be improved.

A C# architecture test library to specify and assert architecture rules in C# for automated testing.

Autoflake removes unused imports and unused variables from Python code.

Check local CloudFormation templates against policy-as-code rules and generate rules from existing templates.

Secure DevOps kit for Azure (AzSK) provides security IntelliSense, Security Verification Tests (SVTs), CICD scan vulnerabilities, compliance issues, and infrastructure misconfiguration in your infrastructure-as-code. Supports Azure via ARM.

A tool to find common security issues in Python code.

Code style enforcement for bash programs. The output format aims to follow pycodestyle (pep8) default output format.

A linting engine supporting custom project-specific rules.

Analyzes a raw binary firmware and determines features like endianness or the loading address. The tool is compatible with all architectures. Loading address: binbloom can parse a raw binary firmware and determine its loading address. Endianness: binbloom can use heuristics to determine the endianness of a firmware. UDS Database: binbloom can parse a raw binary firmware and check if it contains an array containing UDS command IDs.

A binary static analysis tool that provides security and correctness results for Windows portable executables.

Tool to analyze source code and binaries for reusable code, necessary licenses and potential security aspects.

Ever wondered what's making your binary big? Bloaty McBloatface will show you a size profile of the binary so you can understand what's taking up space inside. Bloaty performs a deep analysis of the binary. Using custom ELF, DWARF, and Mach-O parsers, Bloaty aims to accurately attribute every byte of the binary to the symbol or compileunit that produced it. It will even disassemble the binary looking for references to anonymous data. F

Checks whether HTTP response body is closed.

An HTML linter for Bootstrap projects.

Safe code refactoring for modern Python. Bowler is a refactoring tool for manipulating Python at the syntax tree level. It enables safe, large scale code modifications while guaranteeing that the resulting code compiles and runs. It provides both a simple command line interface and a fluent API in Python for generating complex code modifications in code.

A static analysis security vulnerability scanner for Ruby on Rails applications.

Provides a CLI linter that enforces good API design choices and structure

Audit Gemfile.lock for gems with security vulnerabilities reported in Ruby Advisory Database.

C2Rust helps you migrate C99-compliant code to Rust. The translator (or transpiler) produces unsafe Rust code that closely mirrors the input C code.

Code quality threshold checking as part of your build.

Audit Cargo.lock for crates with security vulnerabilities reported to the RustSec Advisory Database.

Find out what takes most of the space in your executable. supports ELF (Linux, BSD), Mach-O (macOS) and PE (Windows) binaries.

cargo-breaking compares a crate's public API between two different branches, shows what changed, and suggests the next version according to semver.

Whole program static stack analysis The tool produces the full call graph of a program as a dot file.

A cargo plugin for linting your dependencies. It can be used either as a command line too, a Rust crate, or a Github action for CI. It checks for valid license information, duplicate crates, security vulnerabilities, and more.

Cargo subcommand to show result of macro expansion and #[derive] expansion applied to the current crate. This is a wrapper around a more verbose compiler command.

Inspect Rust code without syntactic sugar to see what the compiler does behind the curtains.

cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code

Checks all your documentation for spelling and grammar mistakes with hunspell (ready) and languagetool (preview)

Find unused dependencies in Cargo.toml. It either prints out a "unused crates" line listing the crates, or it prints out a line saying that no crates were unused.

Find potential unused enabled feature flags and prune them. You can generate a simple HTML report from the json to make it easier to inspect results. It removes a feature of a dependency and then compiles the project to see if it still compiles. If it does, the feature flag can possibly be removed, but it can be a false-positve.

AWS Labs CloudFormation linter.

A linter for AWS CloudFormation templates.

ct is the the tool for testing Helm charts. It is meant to be used for linting and testing pull requests. It automatically detects charts changed against the target branch.

Pluggable type-checking for Java.

Linter / Analyzer for Makefiles.

Static analysis tool for Terraform files (tf>=v0.12), preventing cloud misconfigs at build time.

Checking Java source code for adherence to a Code Standard or set of validation rules (best practices).

A linter for LaTex which catches some typographic errors LaTeX oversees.

A Project to give the churn file, class, and method for a project for a given checkin. Over time the tool adds up the history of churns to give the number of times a file, class, or method is changing during the life of a project.

Helps discover good candidates for refactoring.

Calculates Chidamber and Kemerer object-oriented metrics by processing the source Java files.

Calculates Chidamber and Kemerer object-oriented metrics by processing the bytecode of compiled Java files.

Vulnerability Static Analysis for Containers.

A code linter to catch common mistakes and improve your Rust code.

A linter for Clojure code that sparks joy. It informs you about potential errors while you are typing.

A compiler tool to increase efficiency, reduce size, and provide code warnings in JavaScript files.

Ensures that all of your project's JavaScript code follows the guidelines in the Google JavaScript Style Guide. It can also automatically fix many common errors.

Clusterlint queries live Kubernetes clusters for resources, executes common and platform specific checks against these resources and provides actionable feedback to cluster operators. It is a non invasive tool that is run externally. Clusterlint does not alter the resource configurations.

An analyzer library for C# and VB that uses Roslyn to produce refactorings, code analysis, and other niceties.

A set of tslint rules for static code analysis of Angular 2 TypeScript projects.

A static analysis tool for Groovy source code, enabling monitoring and enforcement of many coding standards and best practices.

Detects run-time and logic errors.

Check code for common misspellings.

A style checker that helps keep CoffeeScript code clean and consistent.

Checks Java source and byte code for incorrect uses of cryptographic APIs.

A tool for measuring Python class cohesion.

checks if your commit messages meet the conventional commit format

Software complexity analysis for JavaScript projects.

Cookstyle is a linting tool based on the RuboCop Ruby linting tool for Chef cookbooks.

A tool for configurable software verification of C programs. The name CPAchecker was chosen to reflect that the tool is based on the CPA concepts and is used for checking software programs.

Credential Digger is a GitHub scanning tool that identifies hardcoded credentials (Passwords, API Keys, Secret Keys, Tokens, personal information, etc), and filtering the false positive data through a machine learning model called Password Model. This scanner is able to detect passwords and non structured tokens with a low false positive rate.

A static code analysis tool with a focus on code consistency and teaching.

The Crystal compiler has built-in linting functionality.

C# Essentials is a collection of Roslyn diagnostic analyzers, code fixes and refactorings that make it easy to work with C# 6 language features.

Potentially interesting stats on stylesheets.

Does basic syntax checking and finds problematic patterns or signs of inefficiency.

cwe_checker finds vulnerable patterns in binary executables.

Quantifies the cyclomatic complexity of R functions / expressions.

D-Scanner is a tool for analyzing D source code.

Perform static analysis of known vulnerabilities in docker images/containers.

Additional linter for Dart. Reports code metrics, checks for anti-patterns and provides additional rules for Dart analyzer.

A CLI tool to prevent Kubernetes misconfigurations by ensuring that manifests and Helm charts follow best practices as well as your organization’s policies

A static analysis security scanner for ruby written web applications. It supports Sinatra, Padrino and Ruby on Rails frameworks.

dbcritic finds problems in a database schema, such as a missing primary key constraint in a table.

Finds unused code.

Scan Nix files for dead code (unused variable bindings)

Design by contract for Python. Write bug-free code. By adding a few decorators to your code, you get for free tests, static analysis, formal verification, and much more.

An analyzer for JavaScript which targets runtime errors and quality issues rather than coding conventions.

A set of utilities for working with PO files to ease development and improve quality.

Official linter for Deno.

Dependency analysis tool.

Finds usages of deprecated (Symfony) code.

Enforce rules for dependencies between software layers.

Designite supports detection of various architecture, design, and implementation smells, computation of various code quality metrics, and trend analysis.

DesigniteJava supports detection of various architecture, design, and implementation smells along with computation of various code quality metrics.

Detection of design patterns in PHP code.

An enterprise friendly way of detecting and preventing secrets in code. It does this by running periodic diff outputs against heuristically crafted regex statements, to identify whether any new secret has been committed. This way, it avoids the overhead of digging through all git history, as well as the need to scan the entire repository every time.

Static code analysis for Kotlin code.

Mix tasks to simplify use of Dialyzer in Elixir projects.

The DIALYZER, a DIscrepancy AnaLYZer for ERlang programs. Dialyzer is a static analysis tool that identifies software discrepancies, such as definite type errors, code that has become dead or unreachable because of programming error, and unnecessary tests, in single Erlang modules or entire (sets of) applications. Dialyzer starts its analysis from either debug-compiled BEAM bytecode or from Erlang source code. The file and line number of a discrepancy is reported along with an indication of what the discrepancy is about. Dialyzer bases its analysis on the concept of success typings, which allows for sound warnings (no false positives).

Web application (WASM) to render a diff between Rust crate versions.

Strict coding standard for Kotlin and a linter that detects and auto-fixes code smells.

Static analyser for finding deadlocks in Go.

A tool for ensuring Python code is secure.

Lint and validate Dockerfile labels.

Dodgy is a very basic tool to run against your codebase to search for "dodgy" looking values. It is a series of simple regular expressions designed to detect things such as accidental SCM diff checkins, or passwords or secret keys hard coded into files.

Finds assignments/declarations with too many blank identifiers.

Doop is a declarative framework for static analysis of Java/Android programs, centered on pointer analysis algorithms. Doop provides a large variety of analyses and also the surrounding scaffolding to run an analysis end-to-end (fact generation, processing, statistics, etc.).

Linting dotenv files like a charm.

DrNim combines the Nim frontend with the Z3 proof engine in order to allow verify / validate software written in Nim.

Reports potentially duplicated code.

A tool for running Rust lints from dynamic libraries. Dylint makes it easy for developers to maintain their own personal lint collections.

Combine PHP_CodeSniffer and PHP-CS-Fixer.

Linter rules corresponding to the guidelines in Effective Dart

A tool for formally verifying Rust programs by transpiling them into definitions in the Lean theorem prover.

A tool that allows you to analyse your Elm code, identify deficiencies and apply best practices.

Analyzes whole Elm projects, with a focus on shareable and custom rules written in Elm that add guarantees the Elm compiler doesn't give you.

Erlang Style Reviewer.

Linter for Ember or Handlebars templates.