macOS
Homebrewverified · 100%
brew install db-vcsprovider-native install command
brew / rank 17791
Install db-vcs with Homebrew
Version control for MySQL databases. Version 1.1 via Homebrew; verified from local package data.
install
Additional install commands
overview
Package summary
Version control for MySQL databases
Project links
Commands and aliases
- db
history
Project history and usage
db-vcs is a small command-line tool for saving, restoring, and archiving MySQL database snapshots in a project-local repository. It treats database dumps as artifacts that can be named, loaded, exported, and inspected from the shell.
Project history
The GitHub repository was created in April 2019 and the README frames the tool as MySQL-only for now, with extension points for other database systems left as a possibility. Its first public tags, 1.0 and 1.1, are visible in the official repository tag list.
Adoption history
The upstream README documents Homebrew as the macOS installation path and direct cloning for Linux and other systems. That pattern points to a niche developer-tool audience: people who want a lightweight snapshot workflow around migrations and environment refreshes rather than a full migration framework.
How it is used
A typical db-vcs workflow starts with db init, which creates a .db repository in the project root and records connection details. Users then run commands such as db save, db load, db export, db import, db structure, and db log to move database dumps through development, staging, and local recovery scenarios.
Why package nerds care
The package is notable as a Unixy database helper: it wraps mysqldump-style operations in a project repository model, leaves credentials in a predictable ignored file, and exposes everything as simple subcommands. It appeals to package users who prefer shell tools and visible files over a service-backed database workflow.
Timeline
- 2019: Official GitHub repository was created.
- 2019: Tag 1.0 appears in the official repository.
- 2019: Tag 1.1 appears in the official repository.
Related projects
- db-vcs overlaps with database migration and dump tools, but its README positions it around snapshots, restores, imports, exports, and repository-style history rather than schema-only migration management.
Sources
security posture
Risk level: blue
broad file, network, media, or database tool signal.
Risk classifier
blue risk · medium confidence · tool
Why
- broad file, network, media, or database tool signal
Signals
- text:database,sql,version control
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
db | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.1
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:db-vcs |
|---|---|
| Version | 1.1 |
| Package manager | Homebrew |
| Homepage | https://github.com/infostreams/db |
| Repository | https://github.com/infostreams/db |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated package history
- pkgdb category and tag curation