# Install benerator with Homebrew

Tool for realistic test data generation. Version 3.2.1 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:benerator
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install benerator
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:benerator
- **Package manager:** Homebrew
- **Version:** 3.2.1
- **Source summary:** Tool for realistic test data generation
- **Homepage:** <https://rapiddweller.github.io/homebrew-benerator/>
- **Repository:** <https://github.com/rapiddweller/rapiddweller-benerator-ce>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- benerator (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 3.2.1
## Project history and usage

rapiddweller Benerator is a model-driven test-data generation and anonymization tool. It generates realistic, valid, high-volume test data from XML descriptor files and integrations with databases, files, XML, and messaging systems.

### Project history

The current rapiddweller community repository was created in January 2021 as a hard fork and adoption of the older databene-benerator project. The official changelog states that 1.0.0 adopted rapiddweller-benerator-ce, updated and tidied the project, and made no logical changes since databene-benerator 0.9.8 by Volker Bergmann.

The 1.1.0 release moved the repository to GitHub and replaced Oracle Nashorn with GraalVM scripting. Version 2.0.0 added major performance and documentation improvements, while 3.0.0 redesigned parsing, error reporting, execution modes, and platform/domain support. The README now marks Benerator CE as maintenance mode and points new projects to DATAMIMIC.

### Adoption history

Benerator's adoption history spans older SourceForge-era databene users, the rapiddweller fork, Maven/Java distribution, and a later Homebrew formula. Its official README distinguishes existing Benerator CE users from new projects, which are directed toward rapiddweller's DATAMIMIC platform.

The project remains relevant for legacy CI/test-data workflows: the README says Benerator CE keeps working and receives bug fixes, security updates, dependency and CI maintenance, but no new features.

### How it is used

Users describe generation jobs in `benerator.xml` or `*.ben.xml` descriptor files, then run the `benerator` command to generate or anonymize datasets. The official documentation emphasizes descriptor-driven setup and extension.

Typical use cases include generating valid database test data, anonymizing production-like data for tests and demos, creating large interconnected datasets, and integrating with CI tools such as Jenkins and GitLab CI.

### Why package nerds care

Benerator is significant because it is a long-lived Java test-data generator with visible project lineage: databene to rapiddweller, SourceForge to GitLab to GitHub, then maintenance-mode CE alongside a successor platform.

For package managers, it is a useful example of packaging enterprise-adjacent Java tooling for local CLI use, including descriptor files, database drivers, scripting engines, and security-driven dependency maintenance.

### Timeline

- Before 2021: databene-benerator 0.9.8 existed as the predecessor project.
- 2021: rapiddweller-benerator-ce 1.0.0 adopted and forked the databene project.
- 2021: 1.1.0 moved the repository to GitHub and added GraalVM scripting.
- 2021: 2.0.0 improved engine performance and documentation.
- 2022: 3.0.0 introduced major parsing, error-reporting, and execution-mode changes.
- 2024: 3.2.0 introduced a Homebrew formula and additional dataset improvements.
- 2026: 3.3.0 shipped maintenance and hardening work while the README directed new projects to DATAMIMIC.

### Related projects

- databene-benerator is the predecessor project named in the official changelog.
- DATAMIMIC is rapiddweller's successor platform recommended for new projects.
- GraalVM is used for scripting after Nashorn removal.
- Jenkins, GitLab CI, databases, Kafka, and XML/file outputs are part of the documented integration surface.

### Sources

- <https://docs.benerator.de/latest/>
- <https://github.com/rapiddweller/rapiddweller-benerator-ce>
- <https://github.com/rapiddweller/rapiddweller-benerator-ce/blob/development/CHANGELOG.md>
- <https://github.com/rapiddweller/rapiddweller-benerator-ce/releases>
- source_facts.package-manager-url
- source_facts.repo


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: benerator.xml, *.ben.xml

## Combined YAML source

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


## Sources

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