Future of NestBot & Activity Feed integration in OWASP Nest #4422
Unanswered
soghayarmahmoud
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’ve been diving into the OWASP Nest repository and I’m really excited about the direction of the project. I’m particularly interested in the UI/UX overhaul and the introduction of the NestBot assistant.
While looking at the current architecture, I had a couple of technical questions:
For the NestBot (AI Adapter), are you leaning towards a specific provider/LLM, or is the goal to keep it completely agnostic so users can plug in their own keys (like Gemini or OpenAI)? I’ve implemented a similar pluggable layer in a previous project and would love to hear your thoughts on the preferred approach here.
Regarding the OWASP Pulse (Activity Feed), do you have any specific rate-limiting or caching preferences for the GitHub API integration to ensure performance isn't affected?
I’m planning to start working on some UI-related issues to get more familiar with the Tailwind/Next.js setup. If there’s a specific area the team wants to prioritize for the upcoming months, please let me know!
Best regards,
Mahmoud El-Soghayar
All reactions