Skip to content
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
codeql/ruby/
Go to file
codeql/ruby/

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
. .
.vscode
Move files to ruby subfolder
October 15, 2021 11:47
actions/create-extractor-pack
QL/Ruby: included shared extractor code in cache key
May 22, 2023 19:28
doc
Ruby: Update build instructions for new extractor
March 16, 2023 11:54
downgrades
Ruby: add upgrade/downgrade scripts
May 22, 2023 19:37
extractor
Ruby: update grammar
June 9, 2023 16:23
old-change-notes
Move older change notes to old-change-notes
December 14, 2021 12:35
ql
Merge pull request #13426 from jketema/inline-3
June 19, 2023 17:39
scripts
Ruby: Rename extractor to codeql-extractor-ruby
April 19, 2023 06:27
tools
Ruby: Update scripts for merged extractor
April 7, 2023 15:49
.gitattributes
Move files to ruby subfolder
October 15, 2021 11:47
.gitignore
Ruby: Update .gitignore for moved extractor
March 14, 2023 12:03
Makefile
Ruby: Rename extractor to codeql-extractor-ruby
April 19, 2023 06:27
README.md
Ruby: Remove reference to LGTM
December 19, 2022 15:15
codeql-extractor.yml
Ruby: Make trap option title consistent with C#
March 10, 2023 21:11

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).