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/libgepub-0.6.0/tests/test-gepub.c
Examining data/libgepub-0.6.0/libgepub/gepub-widget.h
Examining data/libgepub-0.6.0/libgepub/gepub-widget.c
Examining data/libgepub-0.6.0/libgepub/gepub-utils.h
Examining data/libgepub-0.6.0/libgepub/gepub-text-chunk.c
Examining data/libgepub-0.6.0/libgepub/gepub-archive.h
Examining data/libgepub-0.6.0/libgepub/gepub-text-chunk.h
Examining data/libgepub-0.6.0/libgepub/gepub-utils.c
Examining data/libgepub-0.6.0/libgepub/gepub-doc.c
Examining data/libgepub-0.6.0/libgepub/gepub-doc.h
Examining data/libgepub-0.6.0/libgepub/gepub.h
Examining data/libgepub-0.6.0/libgepub/gepub-archive.c

FINAL RESULTS:

data/libgepub-0.6.0/tests/test-gepub.c:13:21:  [4] (format) printf:
  If format strings can be influenced by an attacker, they can be exploited
  (CWE-134). Use a constant for the format specification.
#define PTEST1(...) printf (__VA_ARGS__)
data/libgepub-0.6.0/libgepub/gepub-doc.c:222:11:  [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 (file);
data/libgepub-0.6.0/tests/test-gepub.c:442:49:  [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).
        gtk_text_buffer_set_text (buffer, buf2, strlen (buf2));

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 3012 in approximately 0.08 seconds (36455 lines/second)
Physical Source Lines of Code (SLOC) = 1937
Hits@level = [0]   5 [1]   2 [2]   0 [3]   0 [4]   1 [5]   0
Hits@level+ = [0+]   8 [1+]   3 [2+]   1 [3+]   1 [4+]   1 [5+]   0
Hits/KSLOC@level+ = [0+] 4.1301 [1+] 1.54879 [2+] 0.516262 [3+] 0.516262 [4+] 0.516262 [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.