Automic VaultAutomic Vault

brew

使用 Homebrew 安装 berkeley-db

查看 berkeley-db 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install berkeley-db

local Homebrew formula metadata

概览

软件包摘要

High performance key/value database

命令和别名

  • db_archive
  • db_checkpoint
  • db_convert
  • db_deadlock
  • db_dump
  • db_hotbackup
  • db_load
  • db_log_verify
  • db_printlog
  • db_recover
  • db_replicate
  • db_stat
  • db_tuner
  • db_upgrade
  • db_verify

历史

项目历史与用法

Berkeley DB is the classic embedded key/value database library lineage now distributed by Oracle. For package-manager users it is less a standalone server than a C library plus administrative utilities whose major version, license, and on-disk compatibility can matter to many dependent packages.

项目历史

Berkeley DB originated in the BSD Unix world and became a general embedded database library under Sleepycat Software. Oracle acquired Sleepycat in 2006, and Oracle's current Berkeley DB pages and documentation now present the product as Oracle Berkeley DB.

The Homebrew berkeley-db package represents the current Oracle Berkeley DB line, with docs for the 18.1 series. It exposes command-line maintenance tools such as db_archive, db_checkpoint, db_dump, db_load, db_recover, db_upgrade, and db_verify in addition to the library API.

采用历史

Berkeley DB's adoption pattern was unusual: many users never chose it directly, but installed it because another package embedded it for local indexes, metadata stores, mail/news databases, directory services, package metadata, or application state.

That indirect adoption made the package-manager story important. Distributions historically carried multiple db, db4, db5, and berkeley-db variants because applications could be tied to a specific ABI or database file format.

使用方式

Developers link Berkeley DB into an application rather than run a database daemon. Runtime state lives in application-controlled database environments, where DB_CONFIG can tune caches, logging, locking, transactions, replication, and recovery behavior.

The bundled tools are operationally important: they let maintainers dump and reload databases, recover environments, inspect logs and statistics, verify files, and upgrade database formats when moving across versions.

为什么软件包爱好者会关心

Berkeley DB is package-nerd canon because it is tiny in concept but huge in dependency consequences. A formula upgrade can affect ABI compatibility, license acceptability, and whether old database files can be opened.

The current brew:berkeley-db and versioned brew:berkeley-db@5 relationship is exactly the sort of thing package historians care about: the unversioned formula tracks the modern Oracle line, while @5 keeps an older major line alive for dependents that cannot simply follow the latest library.

时间线

  • 1990s: Berkeley DB grew out of BSD database code and became Sleepycat Software's embedded database product.
  • 2006: Oracle acquired Sleepycat Software, bringing Berkeley DB under Oracle.
  • 2011: Berkeley DB 5.3 documentation was published for the 11g Release 2 generation.
  • 2018: Oracle Berkeley DB 18.1 documentation represents the later Oracle version-numbering line used by the unversioned berkeley-db package.

Related projects

  • brew:berkeley-db@5 is the versioned Homebrew formula for the older Berkeley DB 5 line.
  • SQLite is a related embedded database alternative, but with a relational SQL model rather than Berkeley DB's key/value API.
  • LMDB is a related embedded key/value store often discussed in the same package and storage-engine context.

安全态势

风险级别:yellow

broad file, network, media, or database tool signal. generalized runtime or code generation signal.

风险分类器

yellow 风险 · 中 置信度 · runtime

原因

  • broad file, network, media, or database tool signal
  • generalized runtime or code generation signal

信号

  • text:backup,archive,database
  • text:repl

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 12 个平台目标。
  • 安装时包含 1 个运行时依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

local files

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

Config paths the tool may read or write during local use.

Unix
<database-environment-home>/DB_CONFIG
Windows
<database-environment-home>\DB_CONFIG

可执行文件

已安装的可执行文件

命令类型暴露范围备注
db_archivecli全局可执行文件
db_checkpointcli全局可执行文件
db_convertcli全局可执行文件
db_deadlockcli全局可执行文件
db_dumpcli全局可执行文件
db_hotbackupcli全局可执行文件
db_loadcli全局可执行文件
db_log_verifycli全局可执行文件
db_printlogcli全局可执行文件
db_recovercli全局可执行文件
db_replicatecli全局可执行文件
db_statcli全局可执行文件
db_tunercli全局可执行文件
db_upgradecli全局可执行文件
db_verifycli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本18.1.40
管理器更新时间2026-06-23
本地数据OK
上游not checked
检测到的最新版本未检测到

https://www.oracle.com/database/technologies/related/berkeleydb.html

安装元数据

软件包元数据

软件包键brew:berkeley-db
版本18.1.40
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/berkeley-db
主页https://www.oracle.com/database/technologies/related/berkeleydb.html
上游文档https://docs.oracle.com/database/bdb181/html/index.html
许可证AGPL-3.0-only
源码归档https://download.oracle.com/berkeley-db/db-18.1.40.tar.gz
最后更新2026-06-23T00:28:31+09:00
Pulseupdated
依赖openssl@3
Bottle可用 (于 arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameberkeley-db
Aliases
  • berkeley-db@18
  • db
Version Scheme0
Revision2
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyyes
URL Keys
  • stable

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment