John Doe

@teja7157 Thanks for reaching out! I would definitely recommend reading the "**Purpose**" section of our README (link below). Additionally, you can check out this video below of Dennis and I...

@teja7157 If the following text from the purpose section of our readme is not what you are looking for, can you be more specific as to what you are looking...

@teja7157 FYI, we just released a new version of **SEDATED®**, with lots of improvements (see below). https://github.com/OWASP/SEDATED/releases/tag/v1.2.0

@BuggaPavanKumar That is really great to hear that you are using SEDATED! As for whitelisting specific keywords, yes this has been something I've been considering already (it's on our enhancements...

@BuggaPavanKumar @sp3nx0r FYI, we just released a new version of **SEDATED®**, with lots of improvements (see below). Potentially what you mentioned above might not be as much of an issue...

@sagarvsh Thanks for reaching out and sorry to hear you are facing this issue. There are a number of both internal and external factors that could be factoring into what...

@sagarvsh Thanks for the additional info. Sounds like whitelisting is still working for you but just very slow and delayed. I have some thoughts, let me know your outcome on...

@sagarvsh Great to hear! Keep us posted if the issues surfaces again and your outcome. We've only experienced this once in the many years we've been running **SEDATED®** so hopefully...

@sagarvsh In that case, if the Github server is not replicating properly then yes it would impact SEDATED white/repo list updates. Ok, that is properly something like a "Known limitation/issue"...

@AsherST excellent, we are reviewing/testing!