Four linters over one repository: how its documents are written, whether every reference resolves, whether the documented interface is the real one, and what a published repository owes a reader.

ISML Linter is a tool for examining if your project's templates follow a specified set of rules defined by your dev team. The available rules can be roughly grouped into:

A command-line tool for validating and enforcing best practices in Docker Compose files.

Linter engine for Perseus

Command-line wrapper for the liquid template language linter.

The world's fastest, most scalable and complete OpenAPI parser

SLDS Linter CLI tool for linting styles and components

Syntax-aware comment wrapping and safe trailing-comment placement for Oxlint.

A tool for formatting bazel BUILD and .bzl files

Configurable linter for package.json files.

Produced-files turn tail: the deliverables row a finished turn ends with

General natural language (tokenizing, stemming (English, Russian, Spanish), part-of-speech tagging, sentiment analysis, classification, inflection, phonetics, tfidf, WordNet, jaro-winkler, Levenshtein distance, Dice's Coefficient) facilities for node.

Default ruleset for the Accord Project Concerto Linter

A liquid template language linter

The webapp is build with React and TypeScript. We use icons from [Lucide](https://lucide.dev/)

Plugin for linting files with Vite

DeepSeek-backed search provider (native web_search via the Anthropic-compatible API) for the DeepSeek Harness web capability seam (ctx.web)

Various JavaScript/TypeScript utilities of wide relevance to the MetaMask codebase

<h1 align="center" style="position: relative;" > <br> <img src="https://github.com/Shopify/theme-check-vscode/blob/main/images/shopify_glyph.png?raw=true" alt="logo" width="141" height="160"> <br> Theme Check </h1>

Remove more unused variables