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/node-webassemblyjs-1.9.1+repack+~cs10.9.15/packages/floating-point-hex-parser/test/fuzzing/parse.c

FINAL RESULTS:

data/node-webassemblyjs-1.9.1+repack+~cs10.9.15/packages/floating-point-hex-parser/test/fuzzing/parse.c:12:2:  [3] (random) srand:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
	srand(time(NULL) + i);
data/node-webassemblyjs-1.9.1+repack+~cs10.9.15/packages/floating-point-hex-parser/test/fuzzing/parse.c:9:10:  [2] (integer) atoi:
  Unless checked, the resulting number can exceed the expected range
  (CWE-190). If source untrusted, check both minimum and maximum, even if the
  input had no minus sign (large numbers can roll over into negative number;
  consider saving to an unsigned value if that is intended).
	int i = atoi(argv[1]);

ANALYSIS SUMMARY:

Hits = 2
Lines analyzed = 24 in approximately 0.08 seconds (287 lines/second)
Physical Source Lines of Code (SLOC) = 16
Hits@level = [0]   1 [1]   0 [2]   1 [3]   1 [4]   0 [5]   0
Hits@level+ = [0+]   3 [1+]   2 [2+]   2 [3+]   1 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 187.5 [1+] 125 [2+] 125 [3+] 62.5 [4+]   0 [5+]   0
Dot directories skipped = 6 (--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.