CodeQL
Named by 20 kept items in this workspace.
17 items name it under tools and 3 under classification.technologies.
The items that name it 20
Static scanner used as equivalent tooling to Semgrep for multi-scanner triage
leading SAST tool for C/C++
Inventories every untrusted-input point and dangerous sink in the codebase so new attack surface must be consciously allow-listed
Independent CI check used on the SecureAI-Scan project itself
Deterministic program analysis tool used as input to guide LLM search space in several hybrid harnesses (e.g. raptor, trailofbits/skills static-analysis)
rule-based static analyzer, contrasted with Argo's LLM-native approach
Proposed future addition for GitHub's semantic code analysis to find deeper vulnerabilities beyond pattern matching
static code analysis / data flow (taint) tracking tool used by Synacktiv to identify RemoteFlowSources and command-injection sinks in the Argo CD Golang codebase, using custom queries and model packs
Required passing security status check before merge in StepSecurity's maintained action branch protection process
Optional but recommended static analysis; interprocedural taint tracking, 8 custom queries for C++ (format string injection, integer truncation, use-after-move, iterator invalidation) and Java (XXE, insecure deserialisation, log injection, Spring SSRF); licence does not permit commercial use
Internal code scanning tooling referenced among leaked internal repos (codeql-docs, codeql-team, code-scanning)
Static analysis / code querying, practical introduction
Static code analyzer cited as part of curl's existing audit tooling
Trail of Bits developed a custom CodeQL query to detect cases where state-changing POST handlers are protected only by read-level permissions
SAST
GitHub code scanning tool; ChainDrop plants a fake codeql_analysis.yml workflow to exfiltrate secrets via toJSON(secrets).
In every workspace you can read 22
Security
All technologies in this workspace.