Automic VaultAutomic Vault

brew

logdy mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install logdy

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#logdy

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

Überblick

Paketzusammenfassung

Web based real-time log viewer

Verlauf

Projektgeschichte und Nutzung

Logdy is a lightweight single-binary log viewer that pipes terminal logs into a local web UI for real-time viewing, filtering, parsing, and exploration.

Projektgeschichte

The official README presents Logdy as a local, zero-dependency single binary with an embedded web UI. Its release history in GitHub begins in early 2024, and the README identifies v0.17.0 as the June 2025 release line.

The project is implemented as a Go backend with embedded UI assets and can also be used as a Go library. Its release process publishes precompiled binaries for Linux, macOS, and Windows-style targets from GitHub releases.

Adoptionsgeschichte

Logdy is young compared with the other packages in this batch. Official project materials frame it around local developer productivity rather than fleet-scale log aggregation: piping `tail -f`, Node.js, Docker, Kubernetes, journalctl, or application output into a browser UI.

Package adoption is still narrow but visible: the supplied metadata records Homebrew and Nix packages, while the README documents Homebrew installation and direct binary downloads from GitHub releases.

Wie es verwendet wird

Typical use is `tail -f file.log | logdy`, `logdy follow app-out.log --full-read`, or `logdy stdin "npm run dev"`. The web UI defaults to localhost port 8080, and the CLI supports modes for stdin, files, sockets, REST forwarding, demos, and utility operations.

Logdy can accept an optional JSON UI config path with `--config`, but the path is user supplied rather than a documented default config-file location. It also exposes flags for an API key, UI password, append-to-file behavior, message buffer size, and analytics/update opt-outs.

Warum Paket-Nerds sich dafür interessieren

Logdy represents the modern single-binary developer-tool pattern: a Go executable embeds a browser UI, ships cross-platform binaries, and becomes useful immediately through a pipe. Package managers make that workflow feel like installing grep or jq, even though the tool launches a local web app.

Zeitleiste

  • 2024: Early public GitHub releases begin, including v0.5.0 in February and v0.13.0 in July.
  • 2025: v0.14.x, v0.15.0, v0.16.0, and v0.17.x releases are published.
  • 2025: README identifies v0.17.0 as the June 1, 2025 latest-version announcement.

Related projects

  • tail, grep, awk, sed, jq, and less: command-line tools used by Logdy's README as workflow comparisons.
  • logdy-ui: the UI project embedded into the logdy-core binary.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 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
logdycliglobales 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-25
Manager-Version0.17.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.17.1

https://github.com/logdyhq/logdy-core

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:logdy
Version0.17.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/logdy
Homepagehttps://logdy.dev
Repositoryhttps://github.com/logdyhq/logdy-core
Upstream-Dokumentationhttps://logdy.dev/docs
LizenzApache-2.0
Quellarchivhttps://github.com/logdyhq/logdy-core/archive/refs/tags/v0.17.1.tar.gz
Build-Abhängigkeitengo
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 Namelogdy
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.

Nix95%

logdy

nix profile install nixpkgs#logdy
  • normalized package name match
  • Abgeglichen nach: Logdy
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/lo/logdy/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