Skip to content
#

static-code-analysis

Here are 430 public repositories matching this topic...

bbatsov
bbatsov commented Dec 2, 2020

There are some annoying warnings when building the documentation site:

$ antora --pull antora-playbook.yml
asciidoctor: WARNING: skipping reference to missing attribute: 1
asciidoctor: WARNING: skipping reference to missing attribute: 3
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: W
documentation good first issue maintenance
semgrep
datree
dimabru
dimabru commented May 17, 2022

Is your feature request related to a problem? Please describe.
the file pkg/defaultRules/defaultRules.yaml is used by our backend as well as the cli itself. Moving it can result in a failure in getting the file for creating new policies in the dashboard

Describe the solution you'd like
Add a step in the ci the verifies that the file pkg/defaultRules/defaultRules.yaml exists (in th

enhancement good first issue up for grabs
reviewdog
davidak
davidak commented Jun 18, 2018

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. create .bandit file with content:
[bandit]
tests: B101,B102,B301

  1. run bandit -c .bandit -r module/
  2. get error:
    [main] ERROR .bandit : Error parsing file.

Expected behavior
working as described in readme

Bandit version

ba
bug good first issue
Pierre-Sassoulas
Pierre-Sassoulas commented May 18, 2022

Current problem

For

result = ''
for number in ['1', '2', '3']:
    result += number  # [consider-using-join]

Where the final result would be "".join(['1', '2', '3']) we already raise a consider-using-join. Sometime function that could be join instead are sneakier, for example:

result = ''
for number in ['1', '2', '3']:
    result += f"{number}
Enhancement Help Wanted 🙏 good first issue High Effort 🏋
revive
zimmski
zimmski commented Apr 7, 2022

Is your feature request related to a problem? Please describe.

When one is using the method "WriteString" of the type "strings::Builder" and does not handle the error it is flagged because all errors must be handled. However, This method never returns an error. Hence, it makes sense to ignore it (even by default).

The problem with revive is, that it does not allow to ignore methods with

msridhar
msridhar commented Jan 22, 2022

This would allow for more localized suppressions. Say we have a method foo(Object o) in an annotated third-party library where o has no type annotation, but o really should be @Nullable, as foo() can handle being passed null as a parameter. In code checked by NullAway, say you write:

void bigMethod() {
  ...
  foo(null); // NullAway reports an error
  ...
}

I beli

Fernal73
Fernal73 commented Nov 2, 2021
[spotbugs] Running SpotBugs...     
    [spotbugs] Unexpected problem occured during version sanity check         
    [spotbugs] Reported exception:         
[spotbugs] java.lang.AbstractMethodError: Receiver class org.slf4j.nop.NOPServiceProvider does not define or inherit an implementation of the resolved method 'abstract java.lang.String getRequesteApiVersion()' of interface org.slf4j.
FullValueRider
FullValueRider commented Dec 10, 2021

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version [Version 2.5.2.6030
OS: Microsoft Windows NT 10.0.22000.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.14701.20226
Host Executable: WINWORD.EXE

Description
Language inspection for assignment of LCase suggests usi

bug enhancement feature-inspections up-for-grabs

Improve this page

Add a description, image, and links to the static-code-analysis topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the static-code-analysis topic, visit your repo's landing page and select "manage topics."

Learn more