# Installer neosync avec Homebrew
Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de neosync pour les workflows d'agents IA.
## installation
```sh
sudo av install brew:neosync
```
Commandes d'installation supplémentaires:
### macOS
- Homebrew (100%):
```sh
brew install neosync
```
Preuve: local Homebrew formula metadata
## Faits du paquet
- **Clé du paquet:** brew:neosync
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.5.41
- **Résumé source:** CLI for interfacing with Neosync
- **Page d'accueil:**
- **Dépôt:**
- **Dernière mise à jour:** 2026-07-26T19:43:14+02:00
- **Généré:** 2026-08-03T19:37:03+00:00
## exécutables
- neosync (alias)
## Comportement d'installation
- Bouteille: non disponible
## Version et fraîcheur
- page générée: 2026-08-03
- version du gestionnaire: 0.5.41
## Historique du projet et usages
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.
### Historique du projet
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.
### Historique d'adoption
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.
### Modes d'utilisation
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.
### Pourquoi les passionnés de paquets s'y intéressent
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.
### Chronologie
- {'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
### Sources
-
-
-
-
-
-
## Notes de sécurité
broad file, network, media, or database tool signal.
- **Risque Geiger:** blue / moyen
- 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)
## Sources
- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph