codeql-skill
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly coherent for CodeQL auditing, but its scan script can automatically run local build commands for a repository and builds those commands from the user-supplied repo path without safe escaping.
Install only if you are comfortable with a CodeQL helper that can run local build commands. Use it on trusted repositories or inside a sandbox/container, and be cautious with repo paths containing unusual shell characters.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Scanning a malicious or oddly named repository could run local build scripts or shell metacharacters on the user's machine, potentially modifying files or using network access.
The user-supplied repo path is interpolated into a build command string that CodeQL will execute. This is purpose-related, but a crafted path or untrusted repository build can cause local command execution beyond simple static analysis.
build_cmd="mvn clean install -DskipTests -f $REPO/pom.xml" ... build_cmd="gradle build -x test -p $REPO" ... build_cmd="make -C $REPO" ... codeql_args+=(--command="$build_cmd")
Document that scanning may execute repository build steps, require explicit user approval for build execution, run scans in a sandbox/container for untrusted repos, and quote or escape repo paths safely when constructing build commands.
The skill may fail or use whatever CodeQL/build tools are available on the user's PATH, which can affect reliability and trust assumptions.
The package metadata does not declare required tools, while the included scan workflow relies on local command-line tools. This is not malicious by itself, but users may not realize what external tooling must be present and trusted.
Required binaries (all must exist): none ... Install specifications: No install spec — this is an instruction-only skill.
Declare CodeQL and optional build-tool requirements in metadata or setup instructions, and recommend trusted/pinned installations where possible.