macOS
Homebrewverified · 100%
brew install logdylocal Homebrew formula metadata
brew
Install logdy with Homebrew, Nix
Web based real-time log viewer. Version 0.17.1 via Homebrew; verified from local package data.
install
Additional install commands
Linux
Nixverified · 92%
nix profile install nixpkgs#logdynixpkgs package indexes · pkgs/by-name/lo/logdy/package.nix · source: api.github.com
overview
Package summary
Web based real-time log viewer
Project links
Commands and aliases
- logdy
history
Project history and usage
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.
Project history
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.
Adoption history
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.
How it is used
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.
Why package nerds care
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.
Timeline
- 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.
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Homebrew bottle metadata is available for 6 platform targets.
- Build metadata lists 1 build dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
logdy | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-07-08
manager version0.17.1
manager updated
local dataok
upstreamcurrent
latest detectedv0.17.1
https://github.com/logdyhq/logdy-core
- infoNo package-manager update timestamp was available.low confidence
install metadata
Package metadata
| Package key | brew:logdy |
|---|---|
| Version | 0.17.1 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/logdy |
| Homepage | https://logdy.dev |
| Repository | https://github.com/logdyhq/logdy-core |
| Upstream docs | https://logdy.dev/docs |
| License | Apache-2.0 |
| Source archive | https://github.com/logdyhq/logdy-core/archive/refs/tags/v0.17.1.tar.gz |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | logdy |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
logdy
nix profile install nixpkgs#logdy- normalized package name match
- Matched by: Logdy
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- 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