codeql
Here are 52 public repositories matching this topic...
-
Updated
Mar 30, 2021
-
Updated
Sep 5, 2021 - Go
This issue relates to the func-style rule.
During the transition from TSLint (now deprecated) to ESLint for typescript linting we introduced some new rules that don't yet pass and added a temporary override in the .eslintrc.json
file to temporarily disable them.
This issue covers removing that temporary override and any changes to the typescript
We should probably run go generate
and other commands that generate code, such as goa gen
, as part of our autobuilder.
Non-printable characters in a results cell are not escaped. Eg- \b
is displayed as what appears to be an empty string.
Two possible solutions that I can think of right now:
- add a quote to all strings that either start or end with a non-printable character
- preprocess all result strings and convert a subset of non-printable chars to their unicode number (ie-
\uXXXX
). We probably onl
-
Updated
Sep 10, 2021 - CodeQL
-
Updated
Aug 24, 2021 - CSS
-
Updated
Dec 11, 2020 - CodeQL
-
Updated
Jun 29, 2021 - Python
-
Updated
Jul 5, 2021 - Dockerfile
-
Updated
Aug 21, 2021 - JavaScript

-
Updated
Feb 14, 2021 - HTML
-
Updated
Sep 2, 2021 - Go
In order to satisfy cpp/windows/wdk/deprecated-api we replaced
ExAllocatePoolWithTag
by ExAllocatePoolZero
and declared macro POOL_ZERO_DOWN_LEVEL_SUPPORT for compilation as code must run downlevel.
However memory is zeroed during allocation now we see false positive
Warning SM02320: Memory allocation of [MyStruct](1) includes uninitialized padding bytes.
Here is example of code
`
-
Updated
Apr 8, 2021
-
Updated
Sep 12, 2021 - Dockerfile
-
Updated
Aug 15, 2021 - TypeScript
-
Updated
Apr 1, 2021
-
Updated
May 1, 2021 - JavaScript
-
Updated
Sep 9, 2021 - Python
Improve this page
Add a description, image, and links to the codeql topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the codeql topic, visit your repo's landing page and select "manage topics."
It appears there are quite a few
http://
links in the documentation and code comments of this project despite the target websites supporting HTTPS (sometimes HTTPS has to be explicitly requested because the website does not upgrade connections on its own).A quick search for
http:
yielded about 4000 findings, however I assume a lot are false positives (e.g. because they are part of an XML n