detekt/detekt

Static code analysis for Kotlin

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 9th, 2026
Created on October 23rd, 2016
Open Issues & Pull Requests: 194 (+0)
GitHub issues: Enabled
Number of forks: 868
Total Stargazers: 7,045 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.1 hours
Mean response time: 25.3 days
90th percentile: 90.3 days
Tracked items: 556

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 56% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "waiting for feedback" is answered fastest, typically in about 12 hours, while "feature" waits about 3 days. 17% of tracked open issues have had no activity in three months. Only 6% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 104
New in 7 days: 3
Closed in 7 days: 2
Avg open age: 655 days
Stale 30+ days: 61
Stale 90+ days: 46

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 2
Events in 7 days: 5

Top labels

  • bug (235)
  • feature (115)
  • help wanted (108)
  • rules (108)
  • never gets stale (72)
  • gradle-plugin (54)
  • stale (54)
  • waiting for feedback (42)

Detailed Description

detekt is a static code analysis tool for Kotlin that identifies code smells and quality issues in Kotlin projects.

The tool addresses the need for automated code quality enforcement in Kotlin codebases by scanning source files against a comprehensive set of configurable rules. It operates by analyzing code patterns and reporting violations through multiple output formats including HTML, Markdown, SARIF, and XML. The approach allows teams to establish and maintain code quality standards without manual review of every pattern.

Teams adopting detekt should consider it if they maintain Kotlin projects and want automated quality gates integrated into their build pipeline. The tool suits projects of any size, from single modules to multi-project builds, with particular value for legacy codebases through its baseline feature, which lets teams suppress existing issues while preventing new ones. The Gradle plugin provides first-party integration, and a community of third-party plugins extends the rule set beyond the built-in offerings. The tool is highly configurable, allowing teams to adjust rule severity and behavior to match their standards, and supports suppression of specific issues through source annotations or baseline files.

The project maintains a healthy balance between core team and community contributions, with open issues reflecting input from both maintainers and external users without creating an unsustainable support burden. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker centers on bugs, feature requests, and rule development, indicating active maintenance focused on stability and expanding detection capabilities.