Clone of the Moby/Docker random name generator as a Python package.
Installation
$ pip install names_generator
Or, with uv:
$ uv add names_generator
Usage
Python API
The API only really consists of a single function.
>>> from names_generator import generate_name
>>> generate_name()
'vigorous_goldstine'
Customize the formatting of the name by specifying a style, one of plain, capital, hyphen, or underscore (default).
>>> generate_name(style='capital')
'Hardcore Thompson'
Pin a seed value for the underlying PRNG to reproduce a given name. A seed is applied to a dedicated PRNG instance, so it never disturbs the global random state on your behalf.
>>> generate_name(seed=42) == generate_name(seed=42)
True
Note that a seed only guarantees reproducibility within a given release. Whenever the underlying name listings change to stay in sync with upstream, some seeds will map to a different name.
Command-line
The package also exposes a basic command-line interface for scripting outside of Python
$ names-generator
clever_matsumoto
$ names-generator --style=capital
Heuristic Einstein
$ names-generator --help
Usage:
names-generator [-h] [-v] [--style NAME]
Generate random name pairing.
Options:
-s, --style NAME Formatting (default: underscore).
-h, --help Show this message and exit.
-v, --version Show the version and exit.
Documentation and issue tracking at:
https://github.com/glentner/names_generator
Because the command matches the distribution name, you can run it without installing anything:
$ uvx names-generator
clever_matsumoto
The command was originally installed as generate_name. That name is still installed and behaves identically, but names-generator is the canonical one and is what the documentation uses.
Development
This project uses uv.
$ uv sync
$ uv run pytest -v --cov
Upstream
The name listings in names_generator/names.py are a direct port of internal/namesgenerator from the Moby project, kept in the same order so the two can be diffed mechanically.
Upstream declared the listing frozen, so no new names are accepted here either. Changes to names.py are only made to bring this port back in sync with upstream.
Metadata
Release files for names-generator 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| names_generator-0.4.0.tar.gz | 12.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| names_generator-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.2 kB
Release files / names_generator-0.4.0.tar.gz
| Download URL | names_generator-0.4.0.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c49046a7c0ab435aa0dfcc8b0bf79b98e8422ad0e1337a1ebaa838224ea72091
|
|
BLAKE2b-256 checksum How to use checksums |
8f3ad34ba188e24e3dae163b612ed856715f3bfded5c49bdba23023f56524278
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / names_generator-0.4.0-py3-none-any.whl
| Download URL | names_generator-0.4.0-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b63610ef5f867197e02d77b9026445dae97dd9277ff8bccac4c8c98d98dfc74
|
|
BLAKE2b-256 checksum How to use checksums |
79d712a52256e98dd4751d12752c570bc7bcbc5bbb4457cbad25e04de4dfd632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log