Love this question...
While I understand that some projects need some sort of privacy for security settings, so this approach makes it feel as being more bound to the users that decide to use it. Wonder how the security section will work? I assume not all the code is going to be public, or will it? How do you plan to handle external attacks to security flaws in the project if it is all public?
There are two approaches to security:
1. Security by obscurity (keep things private, so that attackers don't know about vulnerabilities.
2. Security by sunlight (make everything open, so that any security flaws can be found and fixed)
In opensource approach 1 doesn't work and cryptographers discovered that with good cryptography, it is not even needed, because approach 2 is better.
Bitcoin is a great example. It is totally public, and has become the single most secure software system ever devised. On the other hand, Bitcoin exchanges which are private, and have well paid security teams get hacked all. the. f'king. time.
So we are taking approach no.2. Build well-thought out tech, using well understood cryptography. Make it ALL public and ENCOURAGE people to find flaws in it.
Are there risks? Absolutely. Always DYOR! But this is the only approach that has proven itself in the long run.