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/libjcode-pm-perl-2.06/Unicode/euc2uni.h
Examining data/libjcode-pm-perl-2.06/Unicode/uni.c
Examining data/libjcode-pm-perl-2.06/Unicode/uni2euc.h

FINAL RESULTS:

data/libjcode-pm-perl-2.06/Unicode/uni.c:231:7:  [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).
	IN = fopen(argv[1], "r");
data/libjcode-pm-perl-2.06/Unicode/uni.c:31:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy((char *)dst, offset, 4);
data/libjcode-pm-perl-2.06/Unicode/uni.c:32:8:  [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).
	len = strlen(offset);
data/libjcode-pm-perl-2.06/Unicode/uni.c:213:2:  [1] (buffer) strncpy:
  Easily used incorrectly; doesn't always \0-terminate or check for invalid
  pointers [MS-banned] (CWE-120).
	strncpy((char *)dst, offset, 4);
data/libjcode-pm-perl-2.06/Unicode/uni.c:214:8:  [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).
	len = strlen(offset);

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 11063 in approximately 0.66 seconds (16717 lines/second)
Physical Source Lines of Code (SLOC) = 11032
Hits@level = [0]   1 [1]   4 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   6 [1+]   5 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 0.543872 [1+] 0.453227 [2+] 0.0906454 [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.