Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Automated linting of Cascading Stylesheets
JavaScript Other

README.md

NPM version build status Dependency Status devDependency Status

CSSLint

CSSLint is an open source CSS code quality tool originally written by Nicholas C. Zakas and Nicole Sullivan. It was released in June 2011 at the Velocity conference.

A lint tool performs static analysis of source code and flags patterns that might be errors or otherwise cause problems for the developer.

CSSLint is a tool to help point out problems with your CSS code. It does basic syntax checking as well as applying a set of rules to the code that look for problematic patterns or signs of inefficiency. The rules are all pluggable, so you can easily write your own or omit ones you don't want.

Integration

Command Line Interface

All about the command line interface for CSSLint. If you'd rather use a CLI program to verify your CSS instead of using the web site, then this guide is your best friend. https://github.com/CSSLint/csslint/wiki/Command-line-interface

Build System

Once you're familiar with the CSSLint command line interface, the next step is to integrate it into your build system. This guide walks through using CSSLint as part of your build. https://github.com/CSSLint/csslint/wiki/Build-System-Integration

IDE

You can integrate CSSLint into your favorite IDE to make checking your CSS code quality easy. In fact, some IDEs already have CSSLint built in. https://github.com/CSSLint/csslint/wiki/IDE-integration

Rules

Not sure why a rule is important? This guide talks about each of the CSSLint rules and explains how the rule is designed to improve your CSS. https://github.com/CSSLint/csslint/wiki/Rules

Developer Guide

If you want to contribute to the project, or even just tinker on your own, this guide explains how to get the source and work with it. https://github.com/CSSLint/csslint/wiki/Developer-Guide

Contributors

  1. Samori Gorse, https://twitter.com/shinuza (Rules, Non-zero Exit Code for CLI)
  2. Eitan Konigsburg, https://twitter.com/eitanmk (Rhino CLI)
  3. Ben Barber (Compatible Vendor Prefix Rule)
  4. Eric Wendelin, http://eriwen.com (Output formatters)
  5. Kasper Garnaes, http://reload.dk (Checkstyle XML format)
  6. Gord Tanner, http://www.tinyhippos.com (CLI quiet option)
  7. Hans-Peter Buniat, https://github.com/hpbuniat (Duplicate background image rule)
  8. Dino Chiesa, https://github.com/DinoChiesa (Windows Script Host CLI)
  9. Tomasz Oponowicz, https://github.com/tomasz-oponowicz (XML format and CLI fixes)
  10. Julien Kernec'h, https://github.com/parallel (Fixed a rule)
  11. Cillian de Róiste, https://plus.google.com/116480676247600483573/posts (Node CLI fixes)
  12. Damien Sennm, https://github.com/topaxi (README fixes)
  13. Jonathan Barnett, http://twitter.com/indieisaconcept (JUnit formatter)
  14. Zach Leatherman, http://www.zachleat.com/ (bug fixes)
  15. Philip Walton, http://philipwalton.com (Rules fixes, bug fixes)
  16. Jeff Beck, http://www.jeffbeck.info (Rules fixes, bug fixes)
  17. Jay Merrifield, https://github.com/fracmak (Rules fixes)
  18. Michael Mattiacci, http://mattiacci.com (Rules fixes)
  19. Jonathan Klein, http://www.jonathanklein.net (Bulletproof font-face rule)
  20. Shannon Moeller, http://shannonmoeller.com (Embedded rulesets)
  21. Nick Schonning, https://github.com/nschonni (Contributing.md, grunt build)
  22. Jared Wyles, https://github.com/jaredwy (Managing pull requests, endless advice)
  23. Scott Gonzalez, https://github.com/scottgonzalez (JSON config)
Something went wrong with that request. Please try again.