Learn to say popular static analysis security tool names correctly.
0 / 5 completed
1 / 5
How is Semgrep (static analysis tool for finding code patterns and bugs) correctly pronounced?
Semgrep is pronounced 'SEM-grep' — 'semantic' shortened to 'sem' plus 'grep' (the search tool). Stress on SEM. In a technical interview: "Semgrep flagged every place in the codebase where we were still concatenating raw SQL strings."
2 / 5
How is CodeQL (semantic code analysis engine by GitHub) correctly pronounced?
CodeQL is pronounced 'kohd-KYOO-EL' — 'code' plus 'Q-L' spoken as separate letters. In a technical interview: "CodeQL treats your codebase like a database, so you can write queries to hunt down a whole class of vulnerabilities."
3 / 5
How is Bandit (static analysis security tool for Python) correctly pronounced?
Bandit (the Python security tool) is pronounced 'BAN-dit' — exactly like the everyday word for an outlaw, stress on BAN. In a technical interview: "Bandit caught a hardcoded password sitting in a config file before it ever reached the review."
4 / 5
How is Brakeman (static analysis security scanner for Ruby on Rails) correctly pronounced?
Brakeman is pronounced 'BRAYK-mun' — 'brake' (long A, like a car's brake) plus 'man'. Stress on BRAYK. In a technical interview: "Brakeman warned us about a possible SQL injection hiding in a dynamically built query."
5 / 5
How is SonarQube (continuous code quality and security analysis platform) correctly pronounced?
SonarQube is pronounced 'SOH-nar-kyoob' — 'sonar' (like underwater detection) plus 'cube' spelled Q-U-B-E. Stress on SOH. In a technical interview: "SonarQube blocked the merge because code coverage on the new module had dropped below eighty percent."