# ncc を Homebrew でインストール

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

## インストール

```sh
sudo av install brew:ncc
```

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

### macOS

- Homebrew (100%):

```sh
brew install ncc
```

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:ncc
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.44.1
- **ソース概要:** Compile a Node.js project into a single file
- **ホームページ:** <https://github.com/vercel/ncc>
- **最終更新:** 2026-07-01T00:51:23Z
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- ncc (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

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

ncc is Vercel's zero-config Node.js bundler CLI for compiling a Node module and its dependencies into a single output file, with TypeScript support, asset handling, source maps, minification, externals, cache commands, and programmatic API support.

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

The repository was created on 2018-11-13, with early package distribution under @zeit/ncc on npm the same day. After Zeit became Vercel, @vercel/ncc was created on npm on 2020-08-12 while the old @zeit/ncc package remained visible for legacy users.

The README describes the motivation plainly: publish minimal npm packages, ship only relevant app code to serverless environments, avoid configuring bundlers, reduce boot-time and I/O overhead, and get a compiled-language-like experience for Node programs.

### 採用の歴史

GitHub API data retrieved on 2026-07-01 showed 9,817 stars and 316 forks. The npm downloads API reported 3,712,545 downloads for @vercel/ncc and 56,253 downloads for legacy @zeit/ncc during 2026-05-30 through 2026-06-28.

GitHub's own documentation for creating JavaScript actions names @vercel/ncc alongside Rollup as a way to combine action code and dependencies into one file for distribution, which helped make ncc a common packaging tool in the GitHub Actions ecosystem.

### 使われ方

The standard workflow is ncc build input.js -o dist, producing a compact dist/index.js. Users add flags for minification, source maps, externals, asset builds, TypeScript transpilation, target level, V8 cache output, or license file generation as needed.

Package nerds especially use ncc for JavaScript GitHub Actions and serverless-ish deployment artifacts: commit or publish a small generated dist file instead of vendoring node_modules, while still keeping dependency resolution close to normal Node.js semantics.

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

ncc became the boring answer to 'I need one Node file, not a bundler project.' Its constraint is also its appeal: it targets Node programs, not browser apps, so the command stays small and packaging-oriented.

### タイムライン

- 2018-11-13: vercel/ncc repository created and @zeit/ncc package created on npm.
- 2020-08-12: @vercel/ncc package created on npm.
- 2024-11-15: 0.38.3 release published.
- 2026-06-29: 0.44.1 release published.
- 2026-07-01: Homebrew Formulae reported stable version 0.44.1.

### Related projects

- @zeit/ncc
- GitHub Actions JavaScript actions
- webpack asset relocator

### ソース

- <https://api.github.com/repos/vercel/ncc>
- <https://api.github.com/repos/vercel/ncc/releases>
- <https://api.npmjs.org/downloads/point/last-month/%40vercel/ncc>
- <https://api.npmjs.org/downloads/point/last-month/%40zeit/ncc>
- <https://docs.github.com/actions/tutorials/creating-a-javascript-action>
- <https://formulae.brew.sh/api/formula/ncc.json>
- <https://github.com/vercel/ncc>
- <https://raw.githubusercontent.com/vercel/ncc/main/readme.md>
- <https://registry.npmjs.org/%40vercel/ncc>
- <https://registry.npmjs.org/%40zeit/ncc>


## セキュリティノート

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/ncc.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ncc.yml)


## ソース

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