hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2025-12-17 01:03:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
45f089fda066384aae8d5bc4778067f694594df7
codeql/ruby
History
Nick Rolfe 45f089fda0 Ruby: skip non-existent files in overlay changes JSON 
The previous implementation returned None if any of the paths in the
changes JSON couldn't be canonicalized. This could happen for files that
were deleted in the diff. Now, it just ignores paths for which
canonicalize() fails.
2025-06-23 13:53:18 +01:00
..
.vscode
…
actions/create-extractor-pack
Ruby: update new cargo target directory in make and actions
2024-09-11 11:01:10 +02:00
doc
Fix search paths.
2024-06-03 16:33:17 +02:00
downgrades
Ruby: add databaseMetadata relation to dbscheme
2025-06-19 16:34:15 +01:00
extractor
Ruby: skip non-existent files in overlay changes JSON
2025-06-23 13:53:18 +01:00
old-change-notes
…
ql
Ruby: add databaseMetadata relation to dbscheme
2025-06-19 16:34:15 +01:00
scripts
Ruby: fix extractor pack script after workspace root change
2024-09-11 09:40:44 +02:00
tools
Ruby: Move to new packaging rules.
2024-05-30 14:25:20 +02:00
.gitattributes
…
.gitignore
Exclude consistency output from .gitignore files
2024-09-26 11:09:54 +02:00
BUILD.bazel
Autoformat
2025-02-20 19:31:00 +00:00
codeql-extractor.yml
Ruby: add support for extracting overlays
2025-06-19 16:34:14 +01:00
Makefile
QL tests: run with --check-diff-informed
2025-04-30 10:55:58 -07:00
README.md
Ruby: Remove reference to LGTM
2022-12-19 15:15:43 +00:00

README.md

Ruby analysis support for CodeQL

This directory contains the extractor, CodeQL libraries, and queries that power Ruby support in CodeQL products that GitHub makes available to its customers worldwide.

It contains two major components:

  1. static analysis libraries and queries written in CodeQL that can be used to analyze such a database to find coding mistakes or security vulnerabilities.
  2. an extractor, written in Rust, that parses Ruby source code and converts it into a database that can be queried using CodeQL. See Developer information for information on building the extractor (you do not need to do this if you are only developing queries).