The Wayback Machine - https://web.archive.org/web/20220413192249/https://github.com/topics/static-code-analysis
Skip to content
#

static-code-analysis

Here are 430 public repositories matching this topic...

dvandersluis
dvandersluis commented Sep 16, 2021
~/code/rubocop$ grep -iro "autocorrect" . | wc -l
    1971
~/code/rubocop$ grep -iro "auto-correct" . | wc -l
    1551

Both autocorrect and auto-correct are used frequently in RuboCop. Should we be consistent? If so, which one?

Any change should only affect comments and other string content, not method names.

good first issue
semgrep
bstpierre
bstpierre commented Mar 26, 2022

Describe the bug
Patterns for Go multiple return values match more strictly than the argument list, which is confusing.

To Reproduce
Try to match any Go function that has error in the return type list. All six of these functions should match:

func a(b int) error { return nil }
func b() (int, error) { return 0, nil }
func c() (error, int) { return nil, 0 }
func d() (float6
good first issue priority:low user:external lang:golang
datree
royhadad
royhadad commented Mar 29, 2022

Is your feature request related to a problem? Please describe.
We have a file pkg/policy/defaultRules.yaml - which is the source of truth for the default rules in users' policies.
It's very important we don't break it, therefore - better testing is required.
A quick win would be to test and validate the structure of the yaml

Describe the solution you'd like
Add a test file **pkg/pol

enhancement good first issue WIP testing
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
tushar-deepsource
tushar-deepsource commented Apr 4, 2022

W0402 (deprecated-module) error message says "Uses of a deprecated module 'optparse'".

I think it should say "Use of a deprecated module 'optparse'" instead of "Uses". Either "Use", or "Usage". "Uses" seems grammatically incorrect to me. What do you think?

Help Wanted 🙏 good first issue Documentation 📖
Fernal73
Fernal73 commented Sep 1, 2019

Affects PMD Version:
6.17

Rule:
All rulesets.

Description:
PMD output does not inform the user as to the number of rules contravened while running the tool. The user has to look at the output file.

Code Sample demonstrating the issue:

Sep 01, 2019 9:42:45 AM net.sourceforge.pmd.cache.FileAnalysisCache loadFromFile
INFO: Analysis cache loaded
Sep 01, 2019 9:
an:enhancement good first issue
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