Project Overview
JetBrains intellij-community is the open-source codebase behind IntelliJ IDEA Community Edition and a large part of the IntelliJ Platform. Your team can use it to inspect and modify IDE internals, run the IDE from source, and build plugin functionality on top of platform extension points.
The repository is broad and monorepo-style, with major areas like platform/, plugins/, java/, jps/, and build/. You get source-level access to editor infrastructure, indexing, inspections, refactoring pipelines, and packaging/testing scripts.
This scope gives you deep control, but it also means heavy onboarding cost. Your team should plan for a large checkout, substantial IDE indexing time, and careful branch alignment when Android modules are involved.
Key Challenges Addressed
You often need one consistent IDE runtime that supports many languages, code models, and UI workflows without fragmenting your tooling stack. The IntelliJ Platform approach addresses that by centralizing project models, indexing, PSI/UAST-based code understanding, and shared editor services in one runtime.
You may also need extensibility without carrying a long-lived fork. The platform’s plugin and extension-point model lets your team add inspections, actions, tool windows, and integrations while keeping most customization isolated.
You may need reproducible packaging and test entry points for desktop IDE distribution. The repo includes scriptable build/test paths like installers.cmd and tests.cmd, so your team can wire IDE packaging and test execution into CI pipelines.
Getting Started
The repository README documents a practical bootstrap path. Your team needs Git plus IntelliJ IDEA 2023.2 or newer to open and build from source.
- Clone the repository and enter the project root.
- Pull required Android-related modules with
getPlugins.shorgetPlugins.batwhen your workflow needs them. - Open the root directory in IntelliJ IDEA, resolve required plugins (for example Kotlin when prompted), and run a normal project build.
- Use the predefined
IDEArun configuration to launch the IDE from source.
git clone https://github.com/JetBrains/intellij-community.git
cd intellij-community
./getPlugins.sh
./installers.cmd -Dintellij.build.target.os=current
./tests.cmd -Dintellij.build.test.configurations=ApiCheckTest
Immediate sharp edges to plan for:
- Keep
intellij-communityand Android module checkouts on matching branches/tags when both are present. - GitHub-hosted build workflows for full builds can require larger runners; local builds or prebuilt binaries can be the practical path for personal accounts.
- First open can require enabling or updating bundled IDE plugins before the project sync stabilizes.
Features and Use Cases
You get a full desktop IDE platform with production-grade language tooling internals, not a small plugin sample. That changes what your team can realistically ship.
- Platform internals in
platform/: project model, VFS, indexing, editor, actions, and threading primitives. - Language/tooling modules in areas like
java/,jvm/,xml/, andjson/. - Bundled plugin surface in
plugins/for optional capabilities and integrations. - Build and packaging paths in
build/,installers.cmd, and related scripts. - Test execution entry points in
tests.cmdand IDE run configurations.
Common implementation patterns for your team:
- Build custom inspections and quick-fixes for internal coding standards.
- Create an internal IDE distribution with preconfigured plugins and settings.
- Trace performance or correctness issues by stepping through platform source instead of black-box debugging.
- Contribute upstream fixes when your team hits platform-level defects.
Ecosystem and Dependencies
Your team can treat this repository as the core runtime and pair it with surrounding IntelliJ ecosystem tools.
If your workflow centers on plugin delivery from separate repos, Gradle IntelliJ Plugin can simplify plugin build/test/sign/publish workflows. If your team builds custom language support, Grammar-Kit is a common parser-generation companion inside IntelliJ-oriented stacks. If your team wants a complex reference plugin codebase, intellij-rust is useful for studying large plugin architecture patterns.
Your gain is operational leverage: platform internals in one place, plus external companion tooling for plugin lifecycle management.
Architectural Overview
The repository follows a layered platform-plus-modules shape.
platform/contains core services and UI/runtime foundations.java/,jvm/,xml/,json/,python/, and related directories hold language/tooling implementations.plugins/contains bundled extension modules that plug into platform extension points.jps/and build-related code support project build infrastructure.build/plus top-level build scripts drive packaging and distribution tasks.
At runtime, your team typically works through this flow: project model and file system events feed indexing and caches; code insight and inspections consume those indexes; editor actions and refactorings execute through platform services and plugin extension points. This design matters because you can add functionality at extension boundaries instead of patching core paths, reducing fork pressure and upgrade friction.
Pros and Cons
- Pro: Very deep source visibility for editor, inspections, refactoring, and packaging internals.
- Pro: Mature extension model that supports targeted customization without immediate full-fork commitment.
- Pro: Clear scriptable entry points for packaging and test execution.
- Con: Large codebase and heavy local setup cost for first-time onboarding.
- Con: Build and runtime assumptions can require specific IDE/plugin versions during bootstrap.
- Con: Broad scope means your team needs strong module boundaries internally to avoid fragile custom patches.
Comparison and Alternatives
GitHub stars
Weekly star gains
Full metrics details
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
Intellij Community
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Lapce
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
41 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Issues opened
Weekly total
Full metrics details
GitHub API observation. Historical values render only when the source provides a real observation for that day.
Intellij Community
GitHub API observation. Historical values render only when the source provides a real observation for that day.
38 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub API observation. Historical values render only when the source provides a real observation for that day.
177 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub API observation. Historical values render only when the source provides a real observation for that day.
179 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub API observation. Historical values render only when the source provides a real observation for that day.
39 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Issues closed
Weekly total
Full metrics details
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
Intellij Community
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
38 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
177 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
179 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
39 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Pull requests opened
Weekly total
Full metrics details
GitHub API observation. Historical values render only when the source provides a real observation for that day.
Intellij Community
GitHub API observation. Historical values render only when the source provides a real observation for that day.
38 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub API observation. Historical values render only when the source provides a real observation for that day.
177 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub API observation. Historical values render only when the source provides a real observation for that day.
179 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub API observation. Historical values render only when the source provides a real observation for that day.
39 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Pull requests closed
Weekly total
Full metrics details
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
Intellij Community
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
38 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
177 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
179 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
39 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Pull requests merged
Weekly total
Full metrics details
GitHub API observation. Historical values render only when the source provides a real observation for that day.
Intellij Community
GitHub API observation. Historical values render only when the source provides a real observation for that day.
38 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub API observation. Historical values render only when the source provides a real observation for that day.
177 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub API observation. Historical values render only when the source provides a real observation for that day.
179 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub API observation. Historical values render only when the source provides a real observation for that day.
39 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Open/closed pull request ratio
Weekly average
Full metrics details
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
Intellij Community
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Lapce
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
41 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Open/closed issues ratio
Weekly average
Full metrics details
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
Intellij Community
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Lapce
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
41 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Releases
Weekly total
Full metrics details
GitHub release published_at events bucketed by UTC day; drafts are excluded.
Intellij Community
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscode
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Netbeans
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Eclipse.platform.ui
GitHub release published_at events bucketed by UTC day; drafts are excluded.
81 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Vscodium
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Lapce
GitHub release published_at events bucketed by UTC day; drafts are excluded.
41 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Hotness score
Weekly average
Full metrics details
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
Intellij Community
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Vscode
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Netbeans
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Eclipse.platform.ui
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
81 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Vscodium
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Lapce
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
41 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
- Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
- Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
- Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
- Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
- Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
- Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Reliability score
Weekly average
Full metrics details
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
Intellij Community
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Vscode
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Netbeans
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Eclipse.platform.ui
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
81 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Vscodium
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Lapce
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
41 observed daily rows. Missing days are not fabricated.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
- Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
- Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
- Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
- Support burden = 100 − 2 × open issues per 1,000 stars
- Liveness = 100 × exp(−pushed days ago ÷ 120)
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
If your team is choosing a primary open-source code editor or IDE codebase to extend, credible alternatives include Visual Studio Code, Apache NetBeans, Eclipse Platform UI, VSCodium, and Lapce.
| Project | Repo | Adoption confidence (~6mo) | PRs merged (~6mo) | Star growth (~6mo) |
|---|---|---|---|---|
| IntelliJ IDEA Community | https://github.com/JetBrains/intellij-community | not yet tracked | not yet tracked | not yet tracked |
| Visual Studio Code | https://github.com/microsoft/vscode | metrics pending | 0 | 0 |
| Apache NetBeans | https://github.com/apache/netbeans | 72.92 | 445 | 304 |
| Eclipse Platform UI | https://github.com/eclipse-platform/eclipse.platform.ui | metrics pending | 0 | metrics pending |
| VSCodium | https://github.com/vscodium/vscodium | not yet tracked | not yet tracked | not yet tracked |
| Lapce | https://github.com/lapce/lapce | metrics pending | 0 | metrics pending |
Best overall alternative: Visual Studio Code. You get exceptionally broad extension coverage and mature release/documentation workflows that usually reduce maintenance overhead for day-to-day platform customization.
Conclusion
JetBrains intellij-community is strongest when your team needs direct control over a full IDE platform, from code insight internals to packaging and test automation. The main trade-off is operational weight: onboarding, indexing, and build complexity are materially higher than lightweight editor codebases.
Your most important engineering takeaway is to treat extension points as your default customization boundary, keep forked core patches minimal, and validate changes against upstream workflows documented in the repository, the official IntelliJ Platform SDK docs, and the JetBrains community channels.