pkg.soopen package index

cask

beekeeper-studio mit Homebrew Cask installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrew Caskverifiziert · 100%
brew install --cask beekeeper-studio

local Homebrew cask metadata

Überblick

Paketzusammenfassung

Cross platform SQL editor and database management app

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Verlauf

Projektgeschichte und Nutzung

Beekeeper Studio is a cross-platform SQL editor and database manager begun in 2019 and publicly launched in 2020, emphasizing a fast, uncluttered desktop experience.

Projektgeschichte

Development began in June 2019 as a two-person side project intended to provide a cleaner, more approachable alternative to feature-heavy SQL workbenches.

Beekeeper Studio was introduced publicly in April 2020 and reached a wider developer audience through Hacker News the following month.

In 2022 the project adopted GPLv3 licensing and split into Community and Ultimate editions. The 5.0 work in 2024 returned those editions to a unified application and made its code open source or source available.

Adoptionsgeschichte

An informal April 2020 launch generated early interest, followed by a Hacker News launch in May. By October 2020 the project reported reaching version 1.7 and 3,000 GitHub stars.

The maintainers introduced a separate paid Ultimate Edition in 2022 to fund development. In the 5.0 cycle, the editions were recombined into one application with free and premium capabilities.

Wie es verwendet wird

Developers use Beekeeper Studio to connect to SQL and other supported databases, explore schemas and tables, edit and run queries, retain query history, modify records, and import, export, back up, or restore data.

Saved connections and queries are persisted in a local SQLite database named app.db. Optional INI files provide user-level and administrator-enforced configuration.

Warum Paket-Nerds sich dafür interessieren

Beekeeper Studio occupies the modern, cross-platform end of the database-client ecosystem: it offers native desktop packages for the major operating systems while keeping its main codebase publicly inspectable. Its transition from a free side project to a mixed free/commercial model is also representative of sustainability experiments among open-source desktop tools.

Zeitleiste

  • 2019: Development began in June.
  • 2020: Informal public launch in April and Hacker News launch in May.
  • 2020: Version 1.7 and 3,000 GitHub stars were reported by October.
  • 2022: GPLv3 licensing and the separate Ultimate Edition were announced.
  • 2024: The 5.0 beta unified the editions into one application.

Related projects

  • Beekeeper Studio’s database abstraction work has historical roots in Sqlectron components.
  • It serves a similar role to database clients such as DBeaver, TablePlus, DataGrip, and pgAdmin.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für beekeeper-studio wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

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.

Linux
~/.config/beekeeper-studio/user.config.ini/etc/beekeeper-studio/system.config.ini
macOS
~/Library/Application Support/beekeeper-studio/user.config.ini/Library/Application Support/beekeeper-studio/system.config.ini
Windows
%APPDATA%\beekeeper-studio\user.config.iniC:\ProgramData\beekeeper-studio\system.config.ini

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
~/.config/beekeeper-studio/app.db
macOS
~/Library/Application Support/Beekeeper Studio/app.db
Windows
%APPDATA%\beekeeper-studio\app.db

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
Es waren keine Executable-Daten vorhanden.

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-11-04
Manager-Version6.2.1
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/beekeeper-studio/beekeeper-studio

Installationsmetadaten

Paketmetadaten

Paketschlüsselcask:beekeeper-studio
Version6.2.1
PaketmanagerHomebrew Cask
Paketmanager-Seitehttps://formulae.brew.sh/cask/beekeeper-studio
Homepagehttps://www.beekeeperstudio.io/
Repositoryhttps://github.com/beekeeper-studio/beekeeper-studio
Upstream-Dokumentationhttps://www.beekeeperstudio.io/
Quellarchivhttps://github.com/beekeeper-studio/beekeeper-studio/releases/download/v6.2.1/Beekeeper-Studio-6.2.1-arm64.dmg
SHA-256e7962be7271229dd4a37c39c0a19a90105a0a4c97a54f1c1c8c0194a3c3632ac
Bottlenicht erfasst
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenbeekeeper-studio
Names
  • Beekeeper Studio
Depends On
Artifacts
Auto Updatesyes
Deprecatedno
Disabledno

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

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkgdb category and tag curation