A configurable Ruby tool for linting SCSS files to enforce clean and consistent code style.
SCSS-Lint is a Ruby-based linter for SCSS (Sass) files that analyzes code against configurable rules to enforce style consistency and best practices. It helps developers write cleaner, more maintainable stylesheets by flagging issues like improper indentation, string quote usage, and other common style violations.
Frontend developers and teams working with SCSS/Sass who want to enforce consistent coding standards and improve code quality in their stylesheets.
Developers choose SCSS-Lint for its deep integration with the Ruby Sass ecosystem, extensive configurability, and robust set of built-in linters tailored specifically for SCSS syntax, making it a specialized tool for maintaining style consistency in Sass projects.
Configurable tool for writing clean, consistent SCSS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built specifically for SCSS with over 50 built-in linters for Sass-specific features like nesting and variables, ensuring accurate analysis tailored to SCSS code.
Allows fine-grained control via YAML config, inline comments to disable linters per line or block, and custom severity levels, enabling teams to enforce precise style guides.
Includes native support for Git hooks via overcommit, Rake tasks, Maven plugins, and editor integrations for Vim, Sublime Text, and VS Code, streamlining workflow adoption.
Supports creating custom linters through plugin directories or gems, and allows preprocessing commands to handle cases like Jekyll front matter before linting.
The project relies on Ruby Sass, which the Sass core team has deprecated in favor of Dart Sass, meaning it may not support new Sass features or receive critical updates.
Requires Ruby 2.4+ and gem installation, with monkey patching that can interfere with other Ruby applications, adding setup overhead and potential runtime conflicts.
The README explicitly states it's in sustaining mode with only basic support, making it less suitable for long-term projects compared to actively maintained alternatives like stylelint.
As a SCSS-specific tool tied to a deprecated parser, it lacks the broad community and plugin ecosystem of tools like stylelint, which support multiple CSS languages and modern features.