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/lockfile-progs-0.1.18/lockfile-progs.c

FINAL RESULTS:

data/lockfile-progs-0.1.18/lockfile-progs.c:44:60:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
msg(FILE *f, const char *fmt, ...) __attribute__ ((format (printf, 2, 3)));
data/lockfile-progs-0.1.18/lockfile-progs.c:54:10:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
    rc = vfprintf(f, fmt, args);
data/lockfile-progs-0.1.18/lockfile-progs.c:62:27:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
  __attribute__ ((format (printf, 2, 3)));
data/lockfile-progs-0.1.18/lockfile-progs.c:73:7:  [4] (format) vfprintf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
      vfprintf(stderr, fmt, args);
data/lockfile-progs-0.1.18/lockfile-progs.c:146:23:  [3] (buffer) getopt_long:
  Some older implementations do not protect against internal buffer overflows
  (CWE-120, CWE-20). Check implementation on installation, or limit the size
  of all string inputs.
  while((opt_result = getopt_long(argc, argv,

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 400 in approximately 0.02 seconds (23858 lines/second)
Physical Source Lines of Code (SLOC) = 326
Hits@level = [0]   0 [1]   0 [2]   0 [3]   1 [4]   4 [5]   0
Hits@level+ = [0+]   5 [1+]   5 [2+]   5 [3+]   5 [4+]   4 [5+]   0
Hits/KSLOC@level+ = [0+] 15.3374 [1+] 15.3374 [2+] 15.3374 [3+] 15.3374 [4+] 12.2699 [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.