OS4 DepotLogo by McFly 
(anonymous IP: 3.147.86.143,0) 
 HomeRecentStatsSearchMirrorsContactInfoDisclaimerConfigAdmin
 Menu

 Features
   Crashlogs
   Bug tracker
   Locale browser
 

 Categories

   o Audio (343)
   o Datatype (51)
   o Demo (203)
   o Development (602)
   o Document (24)
   o Driver (97)
   o Emulation (149)
   o Game (1011)
   o Graphics (500)
   o Library (118)
   o Network (234)
   o Office (66)
   o Utility (932)
   o Video (69)

Total files: 4399

Full index file
Recent index file

 Links

  Amigans.net
  OpenAmiga
  Aminet
  UtilityBase
  IntuitionBase
  AmigaBounty


Support the site


 Readme for:  Development » Utility » flawfinder.lha

Flawfinder

Description: Code analysis for potential security flaws
Download: flawfinder.lha       (TIPS: Use the right click menu if your browser takes you back here all the time)
Size: 253kb
Version: 2.0.19r1
Date: 25 Jul 22
Author: David A. Wheeler
Submitter: George Sokianos
Homepage: https://git.walkero.gr/walkero/flawfinder
Requirements: Python
Category: development/utility
License: Other
Distribute: yes
Min OS Version: 4.1
FileID: 12157
 
Comments: 0
Snapshots: 0
Videos: 0
Downloads:  (Current version)
 (Accumulated)

[Show comments] [Show snapshots] [Show videos] [Show content] [Show crashlogs] 
Flawfinder searches through C/C++ source code looking for potential security
flaws.
To run flawfinder, simply give flawfinder a list of directories or files.
For each directory given, all files that have C/C++ filename extensions
in that directory (and its subdirectories, recursively) will be examined.
Thus, for most projects, simply give flawfinder the name of the source
code's topmost directory, and flawfinder will examine all of the project's C/C++
source code.
Flawfinder does fInotfR require that you be able to build your software,
so it can be used even with incomplete source code.

Inside the archive, you will find the documentation in HTML and pdf. Flawfinder
is a python script but it should be able to execute it as a plain command from
anywhere, as long as it is in your path, or by providing its full location.

The very basic way to use it is:
flawfinder src/

There is a way to generate the findings in HTML format as well. Have a look at
the documentation.

Please, let me know what do you think of it and if you find such tools useful.


Copyright (c) 2004-2024 by Björn Hagström All Rights Reserved
Amiga OS and its logos are registered trademarks of Hyperion Entertainment