Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/ibus-input-pad-1.4.2/setup/iconfig-gtk2.h
Examining data/ibus-input-pad-1.4.2/setup/iconfig-gtk2.c
Examining data/ibus-input-pad-1.4.2/setup/main.c
Examining data/ibus-input-pad-1.4.2/setup/setup-gtk2.c
Examining data/ibus-input-pad-1.4.2/setup/setup-gtk2.h
Examining data/ibus-input-pad-1.4.2/engine/engine.h
Examining data/ibus-input-pad-1.4.2/engine/engine.c
Examining data/ibus-input-pad-1.4.2/engine/i18n.h
Examining data/ibus-input-pad-1.4.2/engine/main.c

FINAL RESULTS:

data/ibus-input-pad-1.4.2/setup/setup-gtk2.c:68:30:  [1] (buffer) strlen:
  Does not handle strings that are not \0-terminated; if given one it may
  perform an over-read (it could cause a crash if unprotected) (CWE-126).
                             strlen (ENGINE_INPUT_PAD_SECTION)) != 0) {

ANALYSIS SUMMARY:

Hits = 1
Lines analyzed = 1964 in approximately 0.05 seconds (35765 lines/second)
Physical Source Lines of Code (SLOC) = 1493
Hits@level = [0]   0 [1]   1 [2]   0 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   1 [1+]   1 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 0.669792 [1+] 0.669792 [2+]   0 [3+]   0 [4+]   0 [5+]   0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.