Automic VaultAutomic Vault

brew

Install core-lightning with Homebrew

Lightning Network implementation focusing on spec compliance and performance. Version 26.06.2 via Homebrew; verified 2026-06-29.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install core-lightning

local Homebrew formula metadata

overview

Package summary

Lightning Network implementation focusing on spec compliance and performance

Commands and aliases

  • lightning-cli
  • lightning-hsmtool
  • lightningd
  • reckless

history

Project history and usage

Core Lightning is a C implementation of the Lightning Network protocol that focuses on specification compliance, performance, modularity, and node-operator control. It was formerly known as c-lightning and remains one of the main Lightning node implementations used by technically inclined Bitcoin operators.

Project history

The ElementsProject/lightning repository was created in 2015, during the early implementation period for the Lightning Network. The official README describes Core Lightning, previously c-lightning, as a lightweight, highly customizable, standard-compliant Lightning Network implementation.

The project reached production use on Bitcoin mainnet in early 2018 with the launch of Blockstream Store. Its documentation later standardized on the Core Lightning and CLN names while keeping the same implementation lineage.

Adoption history

Core Lightning adoption has been strongest among node operators, protocol developers, and businesses that want a scriptable daemon, JSON-RPC interface, plugin system, and close tracking of Lightning Network specifications. Its support for plugins and multiple API surfaces makes it especially common in custom node infrastructure.

How it is used

A normal installation runs lightningd alongside a synchronized bitcoind node, then controls it with lightning-cli, JSON-RPC, plugins, or newer API surfaces. Configuration is conventionally stored under ~/.lightning, with network-specific config directories, and the hsm_secret file is the critical wallet-secret material.

Why package nerds care

For package maintainers, Core Lightning is more than a CLI: it ships a daemon, client tools, helper tools, plugins, manpage-style docs, and sensitive runtime state expectations. Packaging has to respect platform support, Bitcoin Core integration, database choices, and key material locations.

Timeline

  • 2015: ElementsProject/lightning repository created.
  • 2018: c-lightning/Core Lightning in production use on Bitcoin mainnet with Blockstream Store.
  • 2020s: Documentation and README use the Core Lightning and CLN names for the former c-lightning project.
  • 2026: v26.06.x releases show continued active upstream maintenance.

Related projects

  • Core Lightning is related to Bitcoin Core, the Lightning Network specifications, other Lightning implementations such as LND and Eclair, and CLN's plugin and RPC ecosystem.

security posture

Risk level: blue

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

Risk classifier

blue risk · medium confidence · tool

Why

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

Signals

  • text:network

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 3 runtime dependencies.
  • Build metadata lists 11 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.

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.

Unix
~/.lightning/config~/.lightning/bitcoin/config

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$LIGHTNINGDIR/hsm_secret

executables

Installed executables

CommandKindExposureNote
lightning-clicliglobal executable
lightning-hsmtoolcliglobal executable
lightningdcliglobal executable
recklesscliglobal 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 version26.06.2
manager updated2026-06-29
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/ElementsProject/lightning

install metadata

Package metadata

Package keybrew:core-lightning
Version26.06.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/core-lightning
Homepagehttps://github.com/ElementsProject/lightning
Repositoryhttps://github.com/ElementsProject/lightning
Upstream docshttps://docs.corelightning.org/docs/home
LicenseMIT
Source archivehttps://github.com/ElementsProject/lightning/releases/download/v26.06.2/clightning-v26.06.2.zip
Last updated2026-06-29T07:58:06Z
Pulseupdated
Dependenciesbitcoin, libsodium, sqlite
Build dependenciesautoconf, automake, gettext, gnu-sed, libtool, lowdown, pkgconf, protobuf, python@3.14, rust, uv
Uses from macOSpython
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

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.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment