codeql/ruby
Cornelius Riemenschneider a66f8209f9 Rust: Vendor 3rdparty dependencies.
We've been observing some performance issues using crate_universe on CI.
Therefore, we're moving to vendor the auto-generated BUILD files
in our repository. This should provide a nice speed boost, while
getting rid of the complexity of the "rust cache" job we've been using
when we had a lot of git dependencies.

This PR includes a vendor script, and I'll put up a CI job internally
that runs that vendor script on Cargo.toml and Cargo.lock changes, to check
that the vendored files are in sync.
2024-11-13 13:22:14 +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: Up/downgrade scripts 2024-06-21 12:04:53 +02:00
extractor Rust: Vendor 3rdparty dependencies. 2024-11-13 13:22:14 +01:00
old-change-notes
ql Post-release preparation for codeql-cli-2.19.3 2024-11-04 17:20:08 +00: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 Ruby: Move to new packaging rules. 2024-05-30 14:25:20 +02:00
Makefile Ruby: update new cargo target directory in make and actions 2024-09-11 11:01:10 +02:00
README.md
codeql-extractor.yml Add supported build modes to extractor metadata 2024-02-06 19:51:13 +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).