Show HN: A free AI risk assessment tool for LLM applications
1. it performs comprehensive AI risk assessments by analyzing your codebase against different AI regulation/framework or even internal policies. It identifies potential issues and suggests fixes directly through one click PRs.
2. the first framework the platform supports is OWASP Top 10 for LLM Applications 2025, upcoming framework will be ISO 42001 as well as custom policy documents.
3. we're a small, early stage team, so the free tier offers 5 assessments per user. If you need more, just reach out, happy to help.
4. sign in via github is required. We request read access to scan code and write access to open PRs for fix suggestions.
5. we are looking for design partners to collaborate with us. If you are looking to build compliance-by-design AI products, we'd love to chat.
product url: https://www.gettavo.com/app
we'd really appreciate feedback on:
- what you like
- what you don't like
- what do you want to see for the next major feature
- bugs
- any other feedback
feel free to comment here or reach out directly: email: percyding@gettavo.com, linkedin: https://www.linkedin.com/in/percy-ding-a43861193/
As a person who works in security in a large enterprise, I'd expect some kind of audit, pentest results, and more available in some type of trust center. And that's before we even send a security questionnaire that digs into your processes and controls.
Though the "Privacy" link on your homepage doesn't work
Do you use scanned repositories for training or other purposes?
-->Do you use scanned repositories for training or other purposes?
No we do not use the scanned repo for training or other purposes
Anyone in the regulation landscape would know that GDPR is a EU data protection law, and PII a US concept which doesn't apply in the GDPR. The GDPR uses the concept of ‘personal data’, not ‘personally identifiable information’. This is not just a wording issue. Redacting, masking, removing information which appears to be ‘personally identifiable’ only constitutes pseudonymisation in the GDPR which does not offer any meaningful privacy protection.
also thanks for flagging the GDPR issue!
Thanks! That's actually an interesting point. We've been trying to reach out to enterprise and get some early users + feedback from them, we will start reaching out to hobby coders or even vibe coder to try out the product as well
Joke or not, it actually made me consider reaching out to vibe coders, but yeah we are still validating the need