You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if one wants to skip a bandit message for "raw" bandit checks (using the bandit executable) in addition to ones done via flake8-bandit, both the noqa and nosec comments need to be used. For example:
assertTrue# noqa: S101 # nosec: B101
The noqa: S101 is required for flake8 to not flag the use of assert, but that's not enough for "raw" bandit. For that the nosec: B101 is needed. But that has no effect on flake8-bandit, so both are needed.
Would be good if the nosec comment was enough for both, maybe flake8-bandit can do something about it?
The text was updated successfully, but these errors were encountered:
scop
added a commit
to scop/hashpipe
that referenced
this issue
Aug 15, 2021
For one config block fewer, run also by tools only aware of flake8 and
not bandit specifically.
Too bad the `nosec: B101` does not seem enough when ran through
flake8-bandit, tylerwince/flake8-bandit#20
Leaving both in for now so raw CLI `bandit` runs get it filtered, too.
Currently if one wants to skip a bandit message for "raw" bandit checks (using the
bandit
executable) in addition to ones done via flake8-bandit, both thenoqa
andnosec
comments need to be used. For example:The
noqa: S101
is required for flake8 to not flag the use ofassert
, but that's not enough for "raw"bandit
. For that thenosec: B101
is needed. But that has no effect on flake8-bandit, so both are needed.Would be good if the
nosec
comment was enough for both, maybe flake8-bandit can do something about it?The text was updated successfully, but these errors were encountered: