-
Updated
Jul 28, 2022 - Haskell
static-analysis
Here are 1,433 public repositories matching this topic...
-
Updated
Jul 29, 2022 - OCaml
-
Updated
Jul 5, 2022 - Java
-
Updated
Jul 30, 2022 - JavaScript
-
Updated
Jul 30, 2022 - PHP
-
Updated
Jul 30, 2022 - Nunjucks
-
Updated
Jul 29, 2022 - Rust
-
Updated
Jul 29, 2022 - PHP
-
Updated
Jul 22, 2022 - Python
-
Updated
Jul 28, 2022 - Go
-
Updated
Jul 20, 2022
-
Updated
Jul 14, 2022 - CMake
-
Updated
Jul 25, 2022 - Haskell
-
Updated
Jul 31, 2022 - Java
Describe the bug
Fingerprint field for results is present in json output but not in sarif output. Sarif specification already has fingerprints and partialFingerprints for this type of values.
To Reproduce
- C
-
Updated
Jul 27, 2022 - Ruby
-
Updated
Jul 22, 2022
-
Updated
Jul 28, 2022 - Go
-
Updated
Jul 30, 2022 - OCaml
-
Updated
Mar 25, 2021 - TypeScript
Many repositories need to fix, so please help if you like.
If you could help, it would be helpful if you could comment before starting the work not to overlapping.
Fix example
Run exit command after lint.
echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go-
Updated
Jul 29, 2022 - PHP
-
Updated
Jul 15, 2022 - Python
-
Updated
Jul 29, 2022 - Go
It is great to be able to run Psalm inside Emacs with output format "emacs". However, some key information about issues are missing, which forces me to run Psalm outside the editor to see them. Of course, this defeats the purpose of the format entirely.
Things that I miss:
- Issue type
- Issue link to psalm.dev
For example, this is what I get inside Emacs:
helpers/Foo.php:168:16:er
-
Updated
Jul 29, 2022 - Go
Improve this page
Add a description, image, and links to the static-analysis topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the static-analysis topic, visit your repo's landing page and select "manage topics."

New Issue Checklist
Describe the bug
Duplicated Key in Dictionary Literal Violationdoes not understand#linedirective.Complete output when running SwiftLint, including the stack trace and command used