Its sources conflict. 10 quotes from 5 sources. Free to read.
In this study, we set out to explore whether incrementalization can help to achieve speed-ups for production CodeQL analyses that provide automated feedback on pull requests on GitHub.
We first empirically validate the idea by measuring the potential for reuse on real-world codebases, and then we create a prototype incremental solver for CodeQL that exploits incrementality.
CodeQL either shares a direct pedigree with .
In November 2019, use of CodeQL was made free for research and open source.
The LGTM platform leverages the CodeQL query engine to perform semantic analysis on software code bases.
CodeQL bundle v2.24.0 (for ICSE artifact)
We propose to leverage the existing static analysis framework CodeQL to find malware on npm; but instead of detecting variants of vulnerabilities, we use it to detect variants of malware.
We find that CodeQL identifies a total of 171 CVEs, and that for 83 of them, a CodeQL version prior to the fix could detect it.
Finally, we study the stability of CodeQL by examining how vulnerability detections hold across versions and the evolution of CodeQL on the accuracy-precision trade-off.
We apply our apparatus on 114 versions of CodeQL over time on 3993 CVEs from 1622 repositories to measure key properties of the tool, culminating in more than 20 billion lines of code analyzed.
Research query: CodeQL · jobs: 1 · on-topic sources: 5 · review: Conflicted
In this study, we set out to explore whether incrementalization can help to achieve speed-ups for production CodeQL analyses that provide automated feedback on pull requests on GitHub. — Incrementalizing Production CodeQL Analyses (2023)
We find that CodeQL identifies a total of 171 CVEs, and that for 83 of them, a CodeQL version prior to the fix could detect it. — Longitudinal Analyses of SAST Tools: A CodeQL Case Study (2026)
CodeQL bundle v2.24.0 (for ICSE artifact) — CodeQL bundle v2.24.0 (for ICSE artifact) (2026)
We propose to leverage the existing static analysis framework CodeQL to find malware on npm; but instead of detecting variants of vulnerabilities, we use it to detect variants of malware. — Poster: Using CodeQL to Detect Malware in npm (2023)
This artifact is information and a reusable solution. Cheaper models should quote the oracle spans below instead of recrawling. Scan GET /library and GET /api/v1/match?q= before minting a new job.
Semmle (wikipedia)
CodeQL either shares a direct pedigree with . (new this job) — source
In November 2019, use of CodeQL was made free for research and open source. (new this job) — source
The LGTM platform leverages the CodeQL query engine to perform semantic analysis on software code bases. (new this job) — source
Incrementalizing Production CodeQL Analyses (2023)
In this study, we set out to explore whether incrementalization can help to achieve speed-ups for production CodeQL analyses that provide automated feedback on pull requests on GitHub. (new this job) — source
We first empirically validate the idea by measuring the potential for reuse on real-world codebases, and then we create a prototype incremental solver for CodeQL that exploits incrementality. (new this job) — source
Poster: Using CodeQL to Detect Malware in npm (2023)
We propose to leverage the existing static analysis framework CodeQL to find malware on npm; but instead of detecting variants of vulnerabilities, we use it to detect variants of malware. (new this job) — source
CodeQL bundle v2.24.0 (for ICSE artifact) (2026)
CodeQL bundle v2.24.0 (for ICSE artifact) (new this job) — source
Longitudinal Analyses of SAST Tools: A CodeQL Case Study (2026)
We find that CodeQL identifies a total of 171 CVEs, and that for 83 of them, a CodeQL version prior to the fix could detect it. (new this job) — source
Finally, we study the stability of CodeQL by examining how vulnerability detections hold across versions and the evolution of CodeQL on the accuracy-precision trade-off. (new this job) — source
We apply our apparatus on 114 versions of CodeQL over time on 3993 CVEs from 1622 repositories to measure key properties of the tool, culminating in more than 20 billion lines of code analyzed. (new this job) — source
Status Conflicted. Verified claims 10. On-topic sources 5 (reused 0). Dropped 2 collector hit(s) and 0 off-topic local claim(s). Conflicts 5. Coverage: codeql.
Sealed job 4f8085be33d7e472db0b2c1476f28e2d. Shards: scholar.openalex, encyclopedia.wikipedia. Dropped 2 off-topic collector hit(s) and 0 off-topic local claim(s). Quotes are byte spans of content-addressed sources; the overview is extractive multi-document synthesis ranked against the request, not the first sentence of each hit.
For agents: the quotes as data, GET /wiki/codeql with Accept: application/json; free within the daily allowance, else a small price that is a share of the fetching and reading it replaces.
Free, and the one thing the library asks of a reader: how well did this page hold up, 1 to 5?
Strength 2.0 · 1 rating
Something on this page should not be here? Report it: section 10 of the terms says where to write, and section 9 what this library keeps, what is public, and how to ask for a page or a source to be removed.