> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/capabilities/code-reviews/code-analysis.md). # Code Analysis ## Overview Nullify analyzes first-party application code and infrastructure to find vulnerabilities before they reach production. It reviews every commit on your default branch and every pull request to catch issues early. Nullify uses both top-down and bottom-up analysis to expose vulnerabilities: * **Top-down analysis** traces user input (HTTP requests, API calls, file uploads) through your application logic to identify unsafe data flows * **Bottom-up analysis** works backward from vulnerable operations (SQL queries, OS commands, serialization) to determine if untrusted data can reach them This dual approach catches injection flaws, authentication bypasses, authorization failures, business logic bugs, and other code-level vulnerabilities that static patterns alone would miss. Nullify also scans infrastructure-as-code (Terraform, CloudFormation, Kubernetes manifests, etc.) for misconfigurations that expose services, weaken access controls, or introduce compliance violations. ## Coverage **Application Code** * Injection flaws (SQL, NoSQL, command, LDAP, XPath, template) * Authentication and authorization failures * Broken access control (IDOR, privilege escalation) * Business logic flaws (race conditions, workflow bypass, price manipulation) * Unsafe deserialization * SSRF and XXE vulnerabilities * Sensitive data exposure and logging **Infrastructure-as-Code** * Exposed services and overly permissive network rules * Weak IAM policies and overprivileged roles * Misconfigured secrets management * Compliance violations (encryption, retention, logging) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nullify.ai/capabilities/code-reviews/code-analysis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.