Code quality suggestion: Consider stricter exception handling

[Fujun-0807]

Hi @cocoindex-io team,

I came across your project while researching code indexing tools – impressive work!

I ran a quick code review using Code Guardian and noticed a few patterns that might be worth addressing:

🎯 Suggestions

1. Exception Handling

Consider using specific exception types instead of broad except: clauses where possible. This helps with:

• Better error messages for users
• Easier debugging
• Preventing silent failures

2. Security Best Practices

• Avoid eval() or exec() if possible (use ast.literal_eval() for safe evaluation)
• Check for hardcoded credentials in config files

💡 Tool Used

Code Guardian – A minimalist code review tool (183 lines, 7 rules, ~5ms analysis).

I'd be happy to run a full scan and share detailed findings if you're interested!

Keep up the great work! 🚀

[badmonster0]

cc @georgeh0 can help take a look, thanks for creating the issue!!

we are hanging out in the discord too if you'd like to join our community :)

[georgeh0]

Thanks for the suggestion! Currently we don't use any broad except: and eval() / exec():

https://github.com/search?q=repo%3Acocoindex-io%2Fcocoindex-code+%2F%5Cb%28except%3A%7Ceval%7Cexec%29%5Cb%2F&type=code