Automic VaultAutomic Vault

brew

dbxml mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für dbxml in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install dbxml

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#dbxml

nixpkgs package indexes · pkgs/by-name/db/dbxml/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Embeddable XML database with XQuery support and other advanced features

Befehle und Aliase

  • dbxml
  • dbxml_dump
  • dbxml_load
  • dbxml_load_container

Verlauf

Projektgeschichte und Nutzung

Berkeley DB XML is Oracle's embeddable XML database product for applications that wanted native XML storage, indexing, and XQuery without running a separate database server. In package terms it sits at the intersection of Berkeley DB, XML databases, and local command-line database tooling.

Projektgeschichte

The project grew out of the Berkeley DB family after native XML databases became a practical answer to document-centric data. Oracle's Programmer's Reference Guide describes Berkeley DB XML as a C++ library built around Berkeley DB storage and XML/XQuery components, with documentation for Unix, Windows, language APIs, upgrades, and the dbxml command-line shell.

Its long manual history is visible in Oracle's upgrade and changelog sections, which cover the 1.2 line, the 2.0 through 2.5 series, and 6.0.x releases. The product's technical story is not only file storage: it was about storing XML documents in containers, indexing nodes and metadata, and running XQuery directly against those containers.

Adoptionsgeschichte

Berkeley DB XML belongs to the embedded-database tradition rather than the client/server database tradition. Oracle's FAQ lists C++, Java, Perl, PHP, Python, and Tcl interfaces, so adoption was mostly through applications that linked the library or scripted it locally, not through users connecting to a network daemon.

The product is also a period marker for the 2000s XML-database wave. It appealed to applications with non-tabular, frequently changing, document-shaped data, where an XML repository reduced the mismatch between the application model and relational tables.

Wie es verwendet wird

Typical use is to create Berkeley DB XML containers, insert XML documents, define indexes, and query them with XQuery or XPath-style expressions. The Homebrew package exposes the dbxml shell and dump/load utilities, which makes it useful for local inspection, export/import, and small reproducible database experiments.

The FAQ emphasizes operational concerns familiar to embedded-database users: large documents, node storage containers, explicit resource cleanup in Java bindings, thread-sharing rules for manager/container/query objects, and careful configuration of validation and external access.

Warum Paket-Nerds sich dafür interessieren

dbxml is a preserved slice of database packaging history: an embeddable XML database installed as libraries plus command-line utilities. It is interesting precisely because it is neither a modern document service nor a plain key-value store; it packages a whole native-XML data-management worldview into a local Unix toolchain.

Zeitleiste

  • 1.2 era: Oracle's guide records Berkeley DB XML 1.2.0 and 1.2.1 changelog sections.
  • 2.x era: Upgrade notes cover 2.0, 2.1, 2.2, 2.3, 2.4, and 2.5 transitions.
  • 2015: Oracle's Berkeley DB XML Programmer's Reference Guide for library version 12.1.6.0 is dated July 10, 2015.
  • 6.0 era: Oracle's documentation includes 6.0.17 and 6.0.18 changelog sections.

Related projects

  • Berkeley DB XML is closely tied to Berkeley DB, XQilla, Xerces-C, and the language bindings documented by Oracle for C++, Java, Perl, PHP, Python, and Tcl.

Sicherheitslage

Risikostufe: orange

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • broad file, network, media, or database tool signal
  • infrastructure mutation or orchestration signal

Signale

  • text:container
  • text:database

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 3 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
dbxmlcliglobales Executable
dbxml_dumpcliglobales Executable
dbxml_loadcliglobales Executable
dbxml_load_containercliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10
Manager-Version6.1.4
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:dbxml
Version6.1.4
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/dbxml
Homepagehttps://www.oracle.com/database/technologies/related/berkeleydb.html
Upstream-Dokumentationhttps://docs.oracle.com/cd/E17276_01/html/programmer_reference_xml/index.html
LizenzAGPL-3.0-only
Quellarchivhttps://download.oracle.com/berkeley-db/dbxml-6.1.4.tar.gz
Zuletzt aktualisiert2026-06-22T14:03:08-07:00
Pulseupdated
Abhängigkeitenberkeley-db, xerces-c, xqilla
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedbxml
Version Scheme0
Revision4
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

dbxml

nix profile install nixpkgs#dbxml
  • normalized package name match
  • Abgeglichen nach: Dbxml
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/db/dbxml/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment