Ross ROSS = Recommend OSS · open-source software intelligence for agents

checkstyle/checkstyle

Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. By default it supports the Google Java Style Guide and Sun Code Conventions, but is highly configurable. It can be invoked with an ANT task and a command line program. observed · 2026-08-28

github.com/checkstyle/checkstyle · homepage · Java · LGPL-2.1 (copyleft) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 98
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 14
  • age_days: 4751
  • days_rel: 15
  • days_push: 7
  • n_releases_24m: 44

Full methodology

Adoption not part of the score

9002 stars · 4179 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Checkstyle is a static analysis tool that checks Java source code against configurable coding standards and style rules, such as naming, imports, Javadoc, formatting, and class design. It ships with a command-line tool and Ant task, supports the Google Java Style Guide and Sun Code Conventions out of the box, and is highly configurable via XML.

Use cases

  • enforce a Java coding standard across a team's codebase
  • check Java code style in CI builds
  • lint Java code for naming and import violations
  • validate Javadoc comments in Java projects
  • run Google Java Style checks on my source files
  • find style violations like fall-through switches and magic numbers
  • integrate code style checking into an Ant or Maven build

When to choose

  • you need automated enforcement of Java coding conventions with highly configurable rules
  • you want built-in support for Google Java Style or Sun Code Conventions
  • you need a mature, actively maintained Java style checker with CLI and build-tool integration

When to avoid

  • you need a formatter that rewrites code automatically rather than reporting violations (use google-java-format)
  • you are linting non-Java languages
  • you need deep semantic or bug-detection analysis rather than style checks (use SpotBugs or Error Prone)

Facets

cli-tool · maturity active

linter static-site-generator developer-tools developer-tools testing jvm cli cross-platform static-analysis code-quality java coding-standards style-checker google-java-style ant-task maven-plugin automation

6 sources

Member repositories

RepositoryRoleHealth v2
checkstyle/checkstylemain99

For agents

markdown · JSON · MCP: product_card(name="checkstyle/checkstyle")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem