# neosync を Homebrew でインストール

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

## インストール

```sh
sudo av install brew:neosync
```

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

### macOS

- Homebrew (100%):

```sh
brew install neosync
```

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:neosync
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.5.41
- **ソース概要:** CLI for interfacing with Neosync
- **ホームページ:** <https://www.neosync.dev/>
- **リポジトリ:** <https://github.com/nucleuscloud/neosync>
- **最終更新:** 2026-07-26T19:43:14+02:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- neosync (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

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

Neosync is the CLI for Neosync, an open-source data anonymization, synthetic data, and environment-sync platform aimed at making production-like data safer to use in development, QA, CI, and local debugging.

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

The `nucleuscloud/neosync` repository was created on 2023-08-24. Its README describes a developer-first platform for anonymizing PII, generating synthetic data, subsetting production databases, preserving referential integrity, and syncing data across environments.

The README also states that Neosync was acquired by Grow Therapy and that the repository is no longer actively maintained. The latest release seen in GitHub metadata was v0.5.41, published on 2025-07-11, which makes the package more of a preserved toolchain entry than an expanding ecosystem package.

### 採用の歴史

The GitHub repository had 4,147 stars and 233 forks when queried on 2026-07-01, showing that the idea attracted open-source attention. Homebrew analytics were tiny by comparison: 1 install in 30 days, 2 in 90 days, and 55 in 365 days for the core formula, so broad Homebrew adoption is weak.

Neosync's adoption path appears to have been more product-led and deployment-led than package-manager-led: Docker Compose, Kubernetes, Helm, GitHub container images, cloud workflows, and docs matter more than a local Homebrew formula.

### 使われ方

The CLI docs show `brew install neosync`, direct release downloads, and Docker images. Typical commands cover login, account inspection, job operations, one-off local syncs, and configuration using an API key or config file.

The practical package use is for developers and platform engineers who need repeatable safe data refreshes: pull anonymized subsets locally, seed development databases, or run sync jobs as part of lower-environment hydration.

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

For av.db, `brew:neosync` should be categorized as a niche but source-backed data-security CLI. Its history is useful mainly because it marks a developer-tool response to stricter PII handling in test data, not because the Homebrew formula itself has large adoption.

### タイムライン

- {'date': '2023-08-24', 'event': 'The `nucleuscloud/neosync` repository was created.'}
- {'date': '2025-07-11', 'event': 'Release v0.5.41 was published.'}
- {'date': '2026-07-01', 'event': 'The upstream README stated that Neosync had been acquired by Grow Therapy and the repository was no longer actively maintained.'}

### Related projects

- Neosync
- nucleuscloud/neosync
- Neosync Helm chart
- ghcr.io/nucleuscloud/neosync/cli

### ソース

- <https://api.github.com/repos/nucleuscloud/neosync>
- <https://artifacthub.io/packages/helm/neosync/neosync>
- <https://formulae.brew.sh/api/formula/neosync.json>
- <https://github.com/nucleuscloud/neosync>
- <https://github.com/nucleuscloud/neosync/blob/main/docs/docs/cli/installing.md>
- <https://github.com/nucleuscloud/neosync/releases>


## セキュリティノート

broad file, network, media, or database tool signal.

- **Geiger リスク:** blue / 中
- broad file, network, media, or database tool signal


## Combined YAML source

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


## ソース

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