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/baloo-widgets-20.04.2/autotests/filemetadatadatedisplaytest.h
Examining data/baloo-widgets-20.04.2/autotests/filemetadatadatedisplaytest.cpp
Examining data/baloo-widgets-20.04.2/autotests/filemetadatawidgettest.h
Examining data/baloo-widgets-20.04.2/autotests/filemetadataitemcounttest.h
Examining data/baloo-widgets-20.04.2/autotests/filemetadatawidgettest.cpp
Examining data/baloo-widgets-20.04.2/autotests/extractortest.cpp
Examining data/baloo-widgets-20.04.2/autotests/extractortest.h
Examining data/baloo-widgets-20.04.2/autotests/filemetadataitemcounttest.cpp
Examining data/baloo-widgets-20.04.2/test/tagwidgetapp.cpp
Examining data/baloo-widgets-20.04.2/test/tagwidgettest.h
Examining data/baloo-widgets-20.04.2/test/metadatawidgetapp.cpp
Examining data/baloo-widgets-20.04.2/test/metadataconfigwidgetapp.cpp
Examining data/baloo-widgets-20.04.2/test/tagwidgettest.cpp
Examining data/baloo-widgets-20.04.2/src/kedittagsdialog.cpp
Examining data/baloo-widgets-20.04.2/src/filemetadataconfigwidget.cpp
Examining data/baloo-widgets-20.04.2/src/filemetadataprovider.cpp
Examining data/baloo-widgets-20.04.2/src/extractorutil_p.h
Examining data/baloo-widgets-20.04.2/src/filemetadataconfigwidget.h
Examining data/baloo-widgets-20.04.2/src/filefetchjob.h
Examining data/baloo-widgets-20.04.2/src/tagwidget.h
Examining data/baloo-widgets-20.04.2/src/tagcheckbox.h
Examining data/baloo-widgets-20.04.2/src/filefetchjob.cpp
Examining data/baloo-widgets-20.04.2/src/filemetadatautil_p.h
Examining data/baloo-widgets-20.04.2/src/keditcommentdialog.cpp
Examining data/baloo-widgets-20.04.2/src/metadatafilter.cpp
Examining data/baloo-widgets-20.04.2/src/tagsfileitemactionplugin/tagsfileitemaction.cpp
Examining data/baloo-widgets-20.04.2/src/tagsfileitemactionplugin/tagsfileitemaction.h
Examining data/baloo-widgets-20.04.2/src/ondemandextractor.cpp
Examining data/baloo-widgets-20.04.2/src/tagcheckbox.cpp
Examining data/baloo-widgets-20.04.2/src/filemetadatawidget.cpp
Examining data/baloo-widgets-20.04.2/src/widgetfactory.cpp
Examining data/baloo-widgets-20.04.2/src/kedittagsdialog_p.h
Examining data/baloo-widgets-20.04.2/src/metadatafilter.h
Examining data/baloo-widgets-20.04.2/src/kcommentwidget.cpp
Examining data/baloo-widgets-20.04.2/src/kblocklayout.cpp
Examining data/baloo-widgets-20.04.2/src/tagwidget.cpp
Examining data/baloo-widgets-20.04.2/src/extractor.cpp
Examining data/baloo-widgets-20.04.2/src/kblocklayout.h
Examining data/baloo-widgets-20.04.2/src/filemetadataprovider.h
Examining data/baloo-widgets-20.04.2/src/kcommentwidget_p.h
Examining data/baloo-widgets-20.04.2/src/keditcommentdialog.h
Examining data/baloo-widgets-20.04.2/src/widgetfactory.h
Examining data/baloo-widgets-20.04.2/src/filepropertiesplugin/baloofilepropertiesplugin.h
Examining data/baloo-widgets-20.04.2/src/filepropertiesplugin/baloofilepropertiesplugin.cpp
Examining data/baloo-widgets-20.04.2/src/ondemandextractor.h
Examining data/baloo-widgets-20.04.2/src/filemetadatawidget.h
Examining data/baloo-widgets-20.04.2/src/filemetadatautil.cpp
Examining data/baloo-widgets-20.04.2/src/tagwidget_p.h

FINAL RESULTS:

data/baloo-widgets-20.04.2/autotests/filemetadatadatedisplaytest.cpp:64:11:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
    file->open(QIODevice::ReadOnly);
data/baloo-widgets-20.04.2/src/extractor.cpp:64:9:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
    out.open(stdout, QIODevice::WriteOnly);
data/baloo-widgets-20.04.2/src/tagwidget.cpp:177:26:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
    d->m_editTagsDialog->open();

ANALYSIS SUMMARY:

Hits = 3
Lines analyzed = 5400 in approximately 0.17 seconds (31520 lines/second)
Physical Source Lines of Code (SLOC) = 3206
Hits@level = [0]   0 [1]   0 [2]   3 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]   3 [1+]   3 [2+]   3 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 0.935745 [1+] 0.935745 [2+] 0.935745 [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.