Contact
Where to send it.
Bugs, questions, and capability requests go to GitHub so the answers stay public and searchable. Security issues have a private path. Anything else reaches the maintainer directly.
- security Open a private advisory
Report a security issue
Use a private GitHub security advisory. Do not open a public issue for a vulnerability — a public issue discloses it the moment you file it.
- bug Open an issue
Report a bug
Include the command you ran, your distribution and architecture, the package name, the Conary version, the source package format, and the exact error. A failure that cannot be reproduced cannot be fixed.
- feature Open an issue
Request a capability
Describe the package or workflow that does not work today rather than the implementation you have in mind. A missing capability model is an engineering defect worth filing precisely.
- question Open a discussion
Ask a question
Questions about how Conary behaves, what is supported today, or whether an approach makes sense belong in Discussions, where the answer stays searchable for the next person.
Everything else
Reach the maintainer
Conary is built by one person. Anything that does not fit above — packaging a project, running Conary somewhere unusual, press, or working together — goes straight to the inbox.
Available for remote engineering work, contract or employed: Rust systems, backend services, and Linux tooling. Open to relocating to Europe.