SAST by Aikido: supported languages and security focus
How Aikido SAST currently works
Aikido’s SAST engine is built to find and prioritize security issues in your code. Unlike traditional SAST tools like SonarQube that focus on code readability, style, and maintainability, Aikido focuses exclusively on security. No noise, just the vulnerabilities you need to fix.
Aikido SAST engine is based on our custom risk categorisation model. Some of these categorisation: -
Aikido removes findings that are not related to security (eg opinionated code styling rules).
Findings that reside in repositories that a user categorized as sensitive will get upgraded.
Findings inside of files that are not intended for production (eg unit tests or functions that aren't used in production) might get downgraded and so on.
Our SAST engine also leverage some of the best open-source engines out there, which we have significantly customized and fine-tuned to provide you sharper, relevant results over the years.
To view all individual rules that are active per language, check out our SAST Checks or Infrastructure as Code checks to view the rules per language.
Language support
Language | Base engine |
---|---|
JavaScript | Aikido Engine + Semgrep |
Typescript | Aikido Engine + Semgrep |
PHP | Aikido Engine + Semgrep |
.NET/C# | Aikido Engine + Semgrep |
Java | Aikido Engine + Semgrep |
Scala | Aikido Engine + Semgrep |
C/C++ | Aikido Engine + Semgrep |
Android | Aikido Engine + Semgrep |
Kotlin | Aikido Engine + Semgrep |
Dart | Aikido Engine + Semgrep |
Go | Aikido Engine + Semgrep |
Ruby | Aikido Engine + Semgrep |
Python | Aikido Engine + Semgrep |
Infrastructure-as-code files (Terraform, Cloudformation, Docker,..) | Checkov |
Exposed secret discovery in all files inside of Git history | Aikido Base Engine with Liveness Checks + Gitleaks |