# gradle-profiler を Homebrew でインストール gradle-profiler のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:gradle-profiler ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install gradle-profiler ``` 証拠: local Homebrew formula metadata ## パッケージ情報 - **パッケージキー:** brew:gradle-profiler - **パッケージマネージャ:** Homebrew - **バージョン:** 0.25.2 - **ソース概要:** Profiling and benchmarking tool for Gradle builds - **ホームページ:** - **リポジトリ:** - **最終更新:** 2026-07-11T11:51:29Z - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - gradle-profiler (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 0.25.2 ## プロジェクトの歴史と使われ方 Gradle Profiler is a Gradle organization tool for repeatedly running builds and collecting benchmarking or profiling data. Its history is best understood as part of the Gradle performance culture rather than as a broad standalone ecosystem. ### プロジェクトの歴史 The official README describes Gradle Profiler as a tool that automates gathering profiling and benchmarking information for Gradle builds. It integrates with build scans, Async Profiler, JProfiler, YourKit, Java Flight Recorder, HPROF heap dumps, Chrome Trace output, and build-operation timing. The project lives under the Gradle GitHub organization and is distributed through release binaries as well as package managers such as Homebrew and SDKMAN. Its 0.x versioning reflects a focused engineering utility rather than a large end-user platform. ### 採用の歴史 Adoption is concentrated among build engineers, Android teams, Gradle plugin authors, and maintainers who need repeatable before-and-after measurements for Gradle version upgrades or build-logic changes. The README's scenario-file support shows the intended workflow: encode a build scenario, run warmups and iterations, then compare outputs. ### 使われ方 Typical usage is `gradle-profiler --benchmark --project-dir ` for timing comparisons, or `gradle-profiler --profile --project-dir ` for deeper profiling. Scenario files in HOCON format support groups, Gradle versions, tasks, daemon modes, mutations, build operation measurements, and IDE sync scenarios. The tool produces benchmark HTML/CSV output and profile artifacts under `profile-out` by default. It can also compare multiple Gradle versions, which makes it useful when a package-manager upgrade changes build behavior. ### パッケージ好きにとっての重要性 Gradle Profiler matters to package nerds because it is the small tool used to decide whether bigger build-tool package changes helped or hurt. It makes Gradle upgrades, Java runtime choices, daemon settings, and cache behavior measurable instead of anecdotal. The Homebrew package is convenient because performance checks often happen on developer workstations before CI jobs or release engineering pipelines adopt a new Gradle line. ### タイムライン - 0.x line: Gradle Profiler releases are published from the Gradle GitHub repository. - 0.23.0: The README identifies this as the last version for builds that require Gradle 5.x support. - 0.24.0: The release notes describe Java 17 as the runtime requirement and Gradle 6.0 as the minimum supported Gradle version. ### Related projects - Gradle Build Tool is the target build system measured by Gradle Profiler. - Develocity and Gradle Build Scan are related analysis surfaces for build performance. - Async Profiler, Java Flight Recorder, JProfiler, YourKit, Chrome Trace, and Perfetto are profiling or visualization tools used by Gradle Profiler. ### ソース - - - ## セキュリティノート narrow executable package without higher-risk signals. - **Geiger リスク:** グリーン / 低 - narrow executable package without higher-risk signals ## Combined YAML source View the package source record on GitHub. [combined/gradle-profiler.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gradle-profiler.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph