|File Search||Catalog||Content Search|
Like RATS, Flawfinder reports are not a direct indication of a vulnerability, but provide a reasonable starting point for performing manual security audits in source code.
Flawfinder can also generate differential reports by pointing it to a patch (diff) file describing the code changes. This way it can be used to determine if the potential flaws found in code have increased or decreased after a commit to a source code management system like CVS or Subversion.
This is "flawfinder" by David A. Wheeler, <firstname.lastname@example.org>. It's a simple Python program for scanning source code for security problems. For more information, see: http://www.dwheeler.com/flawfinder See INSTALL.txt for installation instructions.
FLAWFINDER(1) Flawfinder FLAWFINDER(1) NAME flawfinder - find potential security flaws ("hits") in source code SYNOPSIS flawfinder [--help] [--version] [--allowlink] [--inputs|-I] [ --minlevel X | -m X ] [--falsepositive|-F] [--neverignore|-n] [--patch filename|-P filename] [--followdotdir] [--con‐ text|-c] [--col more»
flawfinder (1.27-3) unstable; urgency=low * Proper distribution as non-native Debian package * Lintian fix release: - debian/control: Move Homepage to a header - debian/copyright: Add the proper copyright, adjust GPL version (it's 2 or later) and point to the actual version 2 file * Use debhelper compatibility version 5 -- Javier Fernandez-Sanguino Pen~a <email@example.com> more»
2007-01-16 David A. Wheeler <dwheeler, at, dwheeler.com> * Release version 1.27 2007-01-16 Sebasti more»
This package was initially debianized by Adam Lazur <firstname.lastname@example.org> on Tue, 30 Oct 2001 09:30:30 -0 more»