contact
Reach the crew.
How to reach the looprig maintainers: email for questions, bug reports, and security disclosures, plus the public discussion and source channels.
Write to crew@looprig.com. That address reaches the maintainers directly and is the right channel for questions the documentation does not answer, for commercial and partnership enquiries, and for anything you would rather not discuss in public.
Please include the module and version you are using, the Go version, the operating system, and the exact command or code path that produced the behaviour you are asking about. A minimal reproduction shortens the round trip more than any other detail.
Bugs and security
Bugs and security
Functional bugs are best filed as issues on the repository that owns the code, at github.com/looprig. Filing against the owning module keeps the report next to the tests and the release tags that would carry the fix.
For a suspected security issue, email crew@looprig.com rather than opening a public issue. Describe the affected module and version, the impact, and the steps to reproduce. We will confirm receipt, investigate, and coordinate a fix and a release before any public description.
Public channels
Public channels
Source, issues, and releases live at github.com/looprig. Longer discussion happens at reddit.com/r/looprig, and short announcements are posted at x.com/xlooprig. Engineering notes are published in the journal on this site and in its RSS feed.
There is no support contract, no ticket queue, and no hosted service behind these addresses. They reach the people who write the code.