# closure-compiler を Homebrew, apt でインストール

closure-compiler のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:closure-compiler
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install closure-compiler
```

  証拠: local Homebrew formula metadata

### Linux

- Debian apt (92%):

```sh
sudo apt install closure-compiler
```

  証拠: Debian stable package indexes: closure-compiler from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

## パッケージ情報

- **パッケージキー:** brew:closure-compiler
- **パッケージマネージャ:** Homebrew
- **バージョン:** 20260726
- **ソース概要:** JavaScript optimizing compiler
- **ホームページ:** <https://developers.google.com/closure/compiler>
- **最終更新:** 2026-07-28T03:32:42Z
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- closure-compiler (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 20260726
## プロジェクトの歴史と使われ方

Closure Compiler is Google's JavaScript checker and optimizer, descended from the Closure Tools release that made Google's internal large-scale JavaScript tooling available to external developers. Its package-manager story is unusual because the compiler is a Java project with Maven distribution, npm wrappers, and OS package formulas rather than a single canonical CLI channel.

### プロジェクトの歴史

Google introduced Closure Tools in 2009, including Closure Compiler, Closure Library, Closure Templates, and Closure Inspector. The compiler's role was to parse JavaScript, perform type and syntax checks, remove dead code, and rewrite code for smaller downloads and faster execution.

The current GitHub repository is maintained by Google and documents the compiler as a whole-program optimizer whose strongest mode, ADVANCED, expects code written with Closure Compiler's assumptions in mind. The README also records the project's long relationship with Closure Library style modules and its more limited fit with modern arbitrary JavaScript bundles.

### 採用の歴史

Google's launch post tied Closure Tools to JavaScript-heavy products such as Gmail, Google Docs, and Google Maps, which made the compiler historically important as a public version of infrastructure used in large browser applications.

Distribution broadened beyond direct Java JAR usage: the upstream README points to Maven artifacts and notes npm/Yarn installation through the separate google-closure-compiler npm packaging maintained outside Google. The Homebrew, Debian, and Ubuntu package-manager facts in the input show that the CLI also became a conventional system package.

### 使われ方

Typical CLI use compiles one or more JavaScript inputs to an output file, with SIMPLE or ADVANCED optimization levels. The compiler can also check types and conformance, transpile newer JavaScript for older browsers, emit source maps, and split output into loadable chunks.

The project is best treated as a specialized optimizer for codebases prepared for its rules, especially when property renaming, externs, and Closure-style module conventions matter.

### パッケージ好きにとっての重要性

Closure Compiler matters to package nerds because it crosses packaging cultures: Java artifacts, npm command wrappers, Linux distro packages, and Homebrew all expose the same optimizer with different expectations about runtime, update cadence, and command names.

It is also a useful example of a package whose canonical upstream warns that one popular distribution path, npm, is built by an outside maintainer from a separate repository, so package provenance matters.

### タイムライン

- 2009: Google introduced Closure Tools and open sourced Closure Compiler.
- 2014: The current google/closure-compiler GitHub repository metadata was created.
- 2024: The README documented deprecation or reduced support for some non-ADVANCED and non-Closure-style module paths.

### Related projects

- Closure Library, Closure Templates, and Closure Inspector were announced with Closure Compiler as related Closure Tools.
- closure-compiler-npm is the separate npm packaging repository named by the upstream README.
- Modern JavaScript bundlers and minifiers overlap with Closure Compiler in SIMPLE-style minification, while Closure Compiler remains distinctive as a whole-program optimizer.

### ソース

- <https://developers.googleblog.com/introducing-closure-tools/>
- <https://developers.google.com/closure/compiler/docs/overview>
- <https://github.com/google/closure-compiler#readme>


## セキュリティノート

closure-compiler に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。


## 他のパッケージマネージャ記録

- Debian apt - closure-compiler - 20130227+rhino-2: normalized package name match | Debian stable package indexes: closure-compiler from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler | https://developers.google.com/closure/compiler/
- Debian apt - libclosure-compiler-java - 20130227+rhino-2: normalized package name match | Debian stable package indexes: libclosure-compiler-java from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler - library package | https://developers.google.com/closure/compiler/
- Debian apt - libclosure-compiler-java-doc - 20130227+rhino-2: normalized package name match | Debian stable package indexes: libclosure-compiler-java-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler - Javadoc | https://developers.google.com/closure/compiler/
- Ubuntu apt - closure-compiler - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: closure-compiler from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler | https://developers.google.com/closure/compiler/
- Ubuntu apt - libclosure-compiler-java - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: libclosure-compiler-java from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler - library package | https://developers.google.com/closure/compiler/
- Ubuntu apt - libclosure-compiler-java-doc - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: libclosure-compiler-java-doc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler - Javadoc | https://developers.google.com/closure/compiler/


## Combined YAML source

View the package source record on GitHub. [combined/closure-compiler.yml](https://github.com/mxcl/pkgdb/blob/main/combined/closure-compiler.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph