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/verse-0.22.8/verse.c

FINAL RESULTS:

data/verse-0.22.8/verse.c:19:1:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
char sstring[10];   /* String to look for */
data/verse-0.22.8/verse.c:27:2:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
	sprintf(sstring,"R%02d%02d",local_time->tm_mon+1,local_time->tm_mday);
data/verse-0.22.8/verse.c:31:4:  [2] (misc) fopen:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	f=fopen(VERSE_LIB,"r");

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 60 in approximately 0.01 seconds (5727 lines/second)
Physical Source Lines of Code (SLOC) = 44
Hits@level = [0]   2 [1]   0 [2]   3 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   5 [1+]   3 [2+]   3 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 113.636 [1+] 68.1818 [2+] 68.1818 [3+]   0 [4+]   0 [5+]   0
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.