Open source is a distinct part of LN Software’s work. These projects make tools available for other developers to inspect, adapt and question. Their repositories remain the source of truth for documentation, releases, supported environments and contribution guidance.
go-mink is a Go toolkit for event sourcing and CQRS, inspired by MartenDB. It provides building blocks for applications that record changes as events and construct read models from that history. The project includes an event store, projections and supporting workflow tools. The documentation is a good starting point for deciding whether the approach fits a particular application.
go-invoice-ninja is a Go SDK for the Invoice Ninja API. It brings operations such as clients, invoices and payments into a Go interface, with configuration for cloud and self-hosted instances. It is an integration library; Invoice Ninja remains the separate product it connects to.
We also maintain a go-llama.cpp fork, descended from go-skynet’s Go bindings and built on the upstream llama.cpp project. That attribution matters. Maintenance extends a shared body of work; it does not make the original engine or bindings an LN invention. Developers should read the build requirements before adopting it, because native compilation and model files are part of the setup.
These repositories solve different problems, so they should not be treated as one required stack. Use the smallest part that helps your application, check its licence and current documentation, and report reproducible issues through the relevant project. A small example, expected behaviour and environment details are often the most useful contribution to begin with.