konveyor/analyzer-lsp

Add-on that is focused on providing analysis based on the Language Server Protocol.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

konveyor/analyzer-lsp has 10+ stars and 50+ forks on GitHub, is written in Go, and was last pushed on Oct 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Added to GitGenius on October 15th, 2026
Created on September 29th, 2022
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 58
Total Stargazers: 18 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.0 hours
Mean response time: 84.9 days
90th percentile: 277.0 days
Tracked items: 187

Maintainer activity

14 people did triage or write work on this repository in the last 12 months.

At least 71% of analyzer-lsp's 14 maintainers work at Red Hat. 11 say where they work, and 10 of those are Red Hat.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "team/insights-discovery" is answered fastest, typically in about 5 hours, while "provider" waits about 3 days. 76% of issues opened in the past year have been closed, leaving a working backlog. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 399 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 10
Events in 7 days: 20

Top labels

  • kind/bug (104)
  • triage/accepted (100)
  • needs-triage (74)
  • needs-priority (67)
  • priority/important-soon (50)
  • provider (43)
  • needs-kind (37)
  • stale (32)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Analyzer LSP is a rule engine that provides code analysis through pluggable providers using the Language Server Protocol.

The tool addresses the need for consistent, language-aware code analysis across multiple programming languages. It works by implementing a rule engine that executes configurable analysis rules against source code, with language-specific providers built on the Language Server Protocol. This approach allows the engine to leverage existing language servers for accurate syntax and semantic understanding rather than implementing language parsing from scratch. Rules are defined in YAML format and can be filtered using label selectors, with analysis results output in a structured format.

Teams should consider this tool when they need to perform custom code analysis across multiple languages within a single framework. It suits projects that require extensible analysis capabilities, particularly those working with Java, Go, Python, Node.js, or YAML codebases. The tool provides both containerized demo environments and source-based execution, making it accessible for quick evaluation or integration into existing workflows. The README does not compare this project to alternative analysis frameworks.

The project maintains automated test coverage across all language providers and the core analyzer engine, with dedicated testing instructions for individual providers. Documentation is comprehensive, covering user-facing configuration of providers and rules alongside developer-focused guides for architecture, setup, and provider development. The codebase builds on established foundations, drawing from the Go language server protocol implementation and Google's JSONRPC2 library while stripping away unnecessary serving and proxy components.