2aba5f1362
Nothing builds this extractor with `cargo` any more: the tests, the extractor pack and the corpus regeneration all go through Bazel. The `cargo` half of the build is now dead weight, and it is not free -- it is a second, independent way of compiling the same Swift code, kept in step by hand. `build.rs` shelled out to `swift build` on the SwiftPM package in `swift/`, scraped `swiftc -print-target-info` for the runtime directory, and emitted the resulting link and rpath flags. Bazel does none of that: it compiles `SwiftSyntaxFFI.swift` directly against `@swift-syntax`, resolved from the Bazel Central Registry. `Package.swift` and `Package.resolved` existed only for that `swift build`. Deleting them collapses three version pins into one. `MODULE.bazel` pinned the toolchain, `.swift-version` pinned it again for `swiftly` and `build.rs`, and `Package.swift` pinned the `swift-syntax` release a second time -- with a comment asking that they be kept in sync and nothing enforcing it. Two Swift builds that could silently diverge become one that cannot. `cargo check` still works, since checking does not link, so rust-analyzer keeps working across the crate -- completion, go-to-definition and inline diagnostics included. What no longer works is `cargo build`/`cargo test`, and hence the editor's "run test" lens; use `bazel test //unified/extractor:all_tests`. The Cargo manifests stay because `misc/bazel/3rdparty` resolves third-party crate versions from them. `scripts/create-extractor-pack.sh` becomes a wrapper around the `codeql_pack` installer that already existed, rather than a parallel cargo-based assembly of the same pack. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 297ff885-7c13-4202-a9d0-bc0b17f68d8e
CodeQL
This open source repository contains the standard CodeQL libraries and queries that power GitHub Advanced Security and the other application security products that GitHub makes available to its customers worldwide.
How do I learn CodeQL and run queries?
There is extensive documentation about the CodeQL language, writing CodeQL using the CodeQL extension for Visual Studio Code and using the CodeQL CLI.
Contributing
We welcome contributions to our standard library and standard checks. Do you have an idea for a new check, or how to improve an existing query? Then please go ahead and open a pull request! Before you do, though, please take the time to read our contributing guidelines. You can also consult our style guides to learn how to format your code for consistency and clarity, how to write query metadata, and how to write query help documentation for your query.
For information on contributing to CodeQL documentation, see the "contributing guide" for docs.
License
The code in this repository is licensed under the MIT License by GitHub.
The CodeQL CLI (including the CodeQL engine) is hosted in a different repository and is licensed separately. If you'd like to use the CodeQL CLI to analyze closed-source code, you will need a separate commercial license; please contact us for further help.
Visual Studio Code integration
If you use Visual Studio Code to work in this repository, there are a few integration features to make development easier.
CodeQL for Visual Studio Code
You can install the CodeQL for Visual Studio Code extension to get syntax highlighting, IntelliSense, and code navigation for the QL language, as well as unit test support for testing CodeQL libraries and queries.
Tasks
The .vscode/tasks.json file defines custom tasks specific to working in this repository. To invoke one of these tasks, select the Terminal | Run Task... menu option, and then select the desired task from the dropdown. You can also invoke the Tasks: Run Task command from the command palette.