pkg.soopen package index

cask

intellij-idea-oss mit Homebrew Cask installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für intellij-idea-oss in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrew Caskverifiziert · 100%
brew install --cask intellij-idea-oss

local Homebrew cask metadata

Überblick

Paketzusammenfassung

Open-source edition of IntelliJ IDEA

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Verlauf

Projektgeschichte und Nutzung

IntelliJ IDEA OSS is JetBrains’ open-source IntelliJ IDEA build, derived from the intellij-community codebase. It provides an extensible IDE centered on Java and Kotlin development.

Projektgeschichte

JetBrains released the first IntelliJ IDEA in January 2001, distinguishing it through advanced Java code navigation and integrated refactoring.

In October 2009, JetBrains announced IntelliJ IDEA Community Edition and open-sourced it under Apache 2.0 alongside the IntelliJ Platform. JetBrains moved the community source code to GitHub in 2011.

JetBrains announced a unified distribution strategy in 2025. The proprietary product became a single installer, while the open-source components remained maintained in the intellij-community repository and available as separately built OSS releases.

Adoptionsgeschichte

The Community Edition gave Java, Groovy, and Scala developers a free Apache-licensed IDE and became the foundation of JetBrains’ open-source IDE ecosystem. JetBrains reported in 2021 that IntelliJ IDEA as a whole was used by more than four million developers.

The IntelliJ Platform and Community codebase also became the foundation for other products, including Android Studio and numerous JetBrains and third-party development tools.

Beginning with the 2025.3 product generation, JetBrains replaced separate Community and Ultimate installers with a unified IntelliJ IDEA distribution while continuing to publish the open-source codebase and open-source builds through GitHub.

Wie es verwendet wird

Developers use IntelliJ IDEA OSS to create, navigate, refactor, test, debug, and version-control software projects. Built-in Gradle and Maven integration makes it especially common for JVM projects, while plugins broaden its language and framework support.

Warum Paket-Nerds sich dafür interessieren

The OSS build matters to package users because it exposes the Apache-licensed core of one of the most influential Java IDEs without the proprietary pieces of JetBrains’ commercial distribution.

Its version-qualified configuration directories, large plugin ecosystem, and role as the upstream platform for other IDEs make upgrades and packaging behavior especially relevant to developers and system maintainers.

Zeitleiste

  • 2001: JetBrains releases the first IntelliJ IDEA.
  • 2009: IntelliJ IDEA Community Edition and the IntelliJ Platform are open-sourced under Apache 2.0.
  • 2011: JetBrains begins hosting the Community Edition and IntelliJ Platform source code on GitHub.
  • 2021: IntelliJ IDEA reaches its twentieth anniversary; JetBrains reports more than four million users.
  • 2025: JetBrains begins the transition to a unified proprietary distribution while retaining GitHub-hosted OSS builds.

Related projects

  • The IntelliJ Platform is the shared application platform underlying IntelliJ IDEA and several other IDEs.
  • Android Studio is built from the IntelliJ Platform and IntelliJ IDEA Community codebase.
  • JetBrains Marketplace supplies plugins that extend the IDE with additional languages, frameworks, and tools.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für intellij-idea-oss wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
~/.config/JetBrains/IntelliJIdea<version>
macOS
~/Library/Application Support/JetBrains/IntelliJIdea<version>
Windows
%APPDATA%\JetBrains\IntelliJIdea<version>

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
Es waren keine Executable-Daten vorhanden.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-11-04
Manager-Version2026.2.4
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/JetBrains/intellij-community

Installationsmetadaten

Paketmetadaten

Paketschlüsselcask:intellij-idea-oss
Version2026.2.4
PaketmanagerHomebrew Cask
Paketmanager-Seitehttps://formulae.brew.sh/cask/intellij-idea-oss
Homepagehttps://github.com/JetBrains/intellij-community
Repositoryhttps://github.com/JetBrains/intellij-community
Quellarchivhttps://github.com/JetBrains/intellij-community/releases/download/idea%2F2026.2.4/idea-2026.2.4-aarch64.dmg
SHA-2568ecd462e120b84e9120c5e20f736784226636fcb8887b3431696f8239a4a740b
Bottlenicht erfasst
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenintellij-idea-oss
Names
  • IntelliJ IDEA OSS
Artifacts
Deprecatedno
Disabledno

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment