15 packages tagged with “linter”
DevSkim is a framework and language analyzer that provides inline security analysis. This is a Dotnet Tool package. For the library package, see Microsoft.CST.DevSkim.
DevSkim is a framework and language analyzer that provides inline security analysis. This is a library package. For the Dotnet Tool package, see Microsoft.CST.DevSkim.CLI.
This package has been moved to Microsoft.CST.DevSkim
A Linter for USFM using USFMToolsSharp
CLI tool for detecting LLM-generated "sloppy" code patterns in .NET projects
Analyzers that should be in the base dotnet compiler
A static analyzer and linter for VRChat UdonSharp scripts that detects common errors and unsupported features
Roslyn analyzer for MudBlazor components with CSS utility linting. Detects inline styles that can be replaced with MudBlazor utility classes for better maintainability and consistency.
Core library for detecting LLM-generated "sloppy" code patterns in .NET projects. Use this library to build custom detection rules, IDE extensions, or integrate slopwatch into your own analysis pipelines.
A SQL Server/T-SQL linter, static analyzer, and formatter
Plugin SDK for TsqlRefine - T-SQL linter and static analyzer
A .NET CLI tool for linting Gherkin feature files in BDD projects. Supports SpecFlow and other BDD frameworks with configurable rules, Git pre-commit hooks, CI/CD integration, and multi-framework support (.NET 6.0, 7.0, 8.0).
A linter for F#.
The package provides static code analysis functions to verify architectural requirements like component structures, layers or dependency rules. At the moment the package is limited to a specific architecture of two concentric layers inspired by the "Clean Architecture" described by Bob Martin. But you can add your own architectural style by implementing the IArchStyle interface.
GDShrapt.Linter provides configurable style checking for GDScript 2.0 (Godot 4.x) with gdtoolkit-compatible suppression. Rule Categories: - Naming: PascalCase, snake_case, SCREAMING_SNAKE_CASE for classes/functions/variables/constants/signals/enums - Style: Line length limits, member ordering, private member prefix (_underscore) - Best Practices: Unused variables/parameters/signals, empty functions, type hint suggestions - Strict Typing (GDL215): Per-element configurable severity for required type hints Key Features: - Comment-based rule suppression (gdtoolkit compatible): gdlint:ignore, gdlint:disable/enable - Configurable severity per rule and per element type - Presets: Default, Strict, Minimal - Support for both rule IDs (GDL001) and names (variable-name) in suppressions Usage: new GDLinter(options).Lint(tree) or LintCode(code) Requires: GDShrapt.Reader