Improve Error Handling Consistency in Scanning Engine #1179
Description
I noticed that the error handling in Nettacker’s scanning engine is inconsistent across core/ and lib. Some functions log errors, others return custom "error" fields, and some silently catch exceptions without providing structured output. To improve clarity and debugging, I want to introduce a small standardized error-handling helper and apply it gradually to affected modules.
Key issues observed:
- no unified error format or helper
- mix of print() and logger usage
- bare except: blocks causing silent failures
- inconsistent return structures on errors
Before opening a PR, I’d like to confirm whether this direction aligns with project goals. If approved, I would be happy to take this up.