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/r-cran-bitops-1.0-6/src/bit-ops.c
Examining data/r-cran-bitops-1.0-6/src/bit-ops.h
Examining data/r-cran-bitops-1.0-6/src/cksum.c

FINAL RESULTS:

data/r-cran-bitops-1.0-6/src/cksum.c:77:22:  [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.
	for ( p = (unsigned char *)strings[i] ; *p ; ++p, len++ ) {

ANALYSIS SUMMARY:

Hits = 1
Lines analyzed = 248 in approximately 0.03 seconds (9264 lines/second)
Physical Source Lines of Code (SLOC) = 203
Hits@level = [0]   0 [1]   0 [2]   1 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   1 [1+]   1 [2+]   1 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 4.92611 [1+] 4.92611 [2+] 4.92611 [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.