Automic VaultAutomic Vault

brew

libsql mit Homebrew, MacPorts, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install libsql

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install libsql

MacPorts ports tree · databases/libsql/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#sqld

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

Überblick

Paketzusammenfassung

Fork of SQLite that is both Open Source, and Open Contributions

Verlauf

Projektgeschichte und Nutzung

libSQL is Turso's open-source, open-contribution fork of SQLite. In package-manager terms it is interesting because it repackages the SQLite model with networked server pieces, embedded replicas, remote access, vector search, and a contribution workflow that differs from upstream SQLite.

Projektgeschichte

Turso documentation describes libSQL as a production-ready fork of SQLite, created because SQLite is open-source but not open-contribution. The project README says libSQL is created and maintained by Turso.

A Turso blog post dated October 3, 2023 says the libSQL project had been announced one year earlier as a fork of SQLite. GitHub release metadata records libsql-0.1.0 on November 22, 2022, matching that origin window.

Adoptionsgeschichte

libSQL adoption is tied to Turso's hosted database service and SDK ecosystem. Turso's docs distinguish libSQL from Turso Database, describing libSQL as the fork that keeps SQLite's file format and API while adding features such as embedded replicas, remote access, and native vector search.

Wie es verwendet wird

Homebrew's libsql package exposes sqld, the server component. Developers use libSQL either as a SQLite-compatible engine with extensions or as part of Turso's remote/replicated SQLite workflow rather than as a general-purpose command-line replacement for sqlite3.

Warum Paket-Nerds sich dafür interessieren

libSQL matters to package nerds because it is a high-profile fork of one of the most depended-on libraries in software. It raises practical packaging questions around SQLite compatibility, server packaging, language SDKs, migration paths, and how far a downstream fork can evolve while preserving the SQLite contract.

Zeitleiste

  • 2022-11-22: GitHub release metadata records libsql-0.1.0.
  • 2023-10-03: Turso wrote that libSQL had been announced one year earlier and was being brought into the Turso family.
  • 2025-01-21: Turso announced a strategic move toward a ground-up SQLite rewrite while describing libSQL as the earlier fork that proved the open-contribution thesis.

Related projects

  • SQLite is the upstream database project and compatibility target.
  • Turso Cloud was built on the libSQL foundation.
  • Turso Database, formerly discussed as a rewrite path, is the same team's separate SQLite-compatible rewrite.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:sql

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhä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
sqldcliglobales 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-08
Manager-Version0.24.32
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/tursodatabase/libsql

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:libsql
Version0.24.32
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/libsql
Homepagehttps://turso.tech/libsql
Repositoryhttps://github.com/tursodatabase/libsql
Upstream-Dokumentationhttps://docs.turso.tech/libsql
LizenzMIT
Quellarchivhttps://github.com/tursodatabase/libsql/releases/download/libsql-server-v0.24.32/source.tar.gz
Build-Abhängigkeitenrust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namelibsql
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

MacPorts95%

libsql

sudo port install libsql
  • normalized package name match
  • Abgeglichen nach: Libsql
MacPorts ports tree · api.github.com · MacPorts ports tree: databases/libsql/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
Nix92%

sqld

nix profile install nixpkgs#sqld
  • installed executable or alias match
  • Abgeglichen nach: Sqld
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/sq/sqld/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