Published code is useful for anybody evaluating what a service actually does rather than what it says, but it is not the same as an audit, and nobody should treat it as a security guarantee. Naven has not published its code.
What Naven does publish instead: exactly what is screened and what is not (navenapp.com/safety), how the screen works and what it costs (navenapp.com/research/screening-before-sending), figures read from its own database with the SQL used to read them (navenapp.com/newsroom/source-floor), measured reliability (navenapp.com/reliability) and live status (navenapp.com/status).
It is built and run independently, which means a short line from feedback to fix, and also no large support team behind it.