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/golang-github-shirou-gopsutil-2.19.11/disk/disk_darwin.c Examining data/golang-github-shirou-gopsutil-2.19.11/disk/disk_darwin.h Examining data/golang-github-shirou-gopsutil-2.19.11/host/freebsd_headers/utxdb.h FINAL RESULTS: data/golang-github-shirou-gopsutil-2.19.11/disk/disk_darwin.h:11:2: [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 name[NAMELEN+1]; data/golang-github-shirou-gopsutil-2.19.11/host/freebsd_headers/utxdb.h:53:2: [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 fu_id[8]; data/golang-github-shirou-gopsutil-2.19.11/host/freebsd_headers/utxdb.h:55:2: [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 fu_user[32]; data/golang-github-shirou-gopsutil-2.19.11/host/freebsd_headers/utxdb.h:56:2: [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 fu_line[16]; data/golang-github-shirou-gopsutil-2.19.11/host/freebsd_headers/utxdb.h:57:2: [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 fu_host[128]; data/golang-github-shirou-gopsutil-2.19.11/disk/disk_darwin.c:91:69: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). {kIOBlockStorageDriverStatisticsBytesReadKey, offsetof(DriveStats, read)}, data/golang-github-shirou-gopsutil-2.19.11/disk/disk_darwin.h:15:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). int64_t read; ANALYSIS SUMMARY: Hits = 7 Lines analyzed = 227 in approximately 0.05 seconds (4291 lines/second) Physical Source Lines of Code (SLOC) = 159 Hits@level = [0] 0 [1] 2 [2] 5 [3] 0 [4] 0 [5] 0 Hits@level+ = [0+] 7 [1+] 7 [2+] 5 [3+] 0 [4+] 0 [5+] 0 Hits/KSLOC@level+ = [0+] 44.0252 [1+] 44.0252 [2+] 31.4465 [3+] 0 [4+] 0 [5+] 0 Dot directories skipped = 3 (--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.