dsoftbus_safety_guard

To perform a security code review on OpenHarmony dsoftbus C/C++ sources, run this skill on your target directory to detect unsafe coding patterns and generate a detailed read-only report. It applies 40+ safety rules across pointer, memory, lock, and fd categories.

You can detect memory safety and pointer vulnerabilities in dsoftbus IPC and network code using built-in rules for null dereferences, buffer misuse, and lock leaks. The analysis traces cross-file call chains and control-flow paths to uncover path-sensitive defects.

Cross-file control-flow analysis helps find security risks in multithreaded C/C++ code by tracing resource and data flows across files. This path-sensitive execution analysis uncovers defects like lock leaks and unsafe return patterns that single-file reviews often miss.

Yes, this code review tool checks for sensitive information leaking through logs by enforcing logging policy compliance rules. It identifies unsafe log output patterns and prevents sensitive data from being exposed in dsoftbus components.

No, you cannot use this to automatically fix null dereferences and lock leaks because it generates a read-only review report. It provides actionable fix suggestions within the report output without modifying your original source files.

A limitation of using automated safety rules for external input validation in C/C++ is that the review is read-only and does not modify files. It focuses on detecting predefined unsafe patterns across permission and input categories rather than runtime dynamic testing.