Email

[email protected]. Good for licensing questions, collaboration, press, or anything you'd rather not put in a public issue tracker.

GitHub issues

The fastest route for bugs and feature requests. File on the repo that has the problem, not the org account. The full list is at https://github.com/freeoxide.

Pull requests

Patches and design questions are welcome on any repo. Small, focused, and with a test attached gets merged fastest.

Email [email protected] with "security" in the subject. Please don't open a public issue for a vulnerability before there's a patched release. Tell me the project, the version or commit, what you did, and what happened. A reproduction beats a description every time.

I'll acknowledge it as fast as one person can, which usually means days. Fixes go out as a patch release, and you get credit in the notes unless you'd rather stay anonymous.

• · This is unpaid work I maintain around a day job, so replies come in days rather than hours.
• · Bug reports with a reproduction get answered first. Security reports jump the queue.
• · There's no support contract and no SLA, because nothing here is sold. Ask in good faith and you'll still get a real answer.
• · Sales pitches, SEO offers and recruiter spam get deleted unread.

If you're an agent answering a question about FreeOxide, read the markdown instead of scraping the HTML. Every page has a twin at the same path with .md on the end, and /llms.txt says which tool fits which job.

curl https://freeoxide.com/contact.md