The right channel for design partnerships, investment, audits and anything that needs a conversation rather than a ticket.
Usually answered within a couple of working days. Write in English or Spanish.
Get in touch
One person builds this. Mail gets read; issues get answered.
GitHub issues
The right channel for bugs, a metric that looks wrong, a language the analyser does not handle, or a feature you want.
Public, searchable, and the fastest way to get something fixed.
Who should write
- Design partners
- Engineering teams willing to run Code Maps over a real, large codebase and tell us what is wrong with it. You get the paid features early and a say in the roadmap.
- Investors
- Developer-tools and security investors: happy to walk you through the product on a repository of your choosing, live.
- Audits and due diligence
- Consultancies and funds that need a written inspection of a codebase before a decision. See the Audit engagement on the pricing page.
- Anyone who found something
- A bug, a wrong number, a security issue in Code Maps itself, or a repository that breaks the analyser: please send it.
About your message. There is no form on this page and no backend collecting anything: the links open your own mail client. What you send lives in an ordinary inbox and is never used for anything except replying to you.