Open Source OCaml (Objective Caml) Source Code Analysis Tools

Static analysis at ludicrous speed. Find bugs and enforce code standards. Find and prevent security issues in Terraform, Docker, Kubernetes, nginx, and AWS configs before they go into production. Go beyond application code and protect the entire stack with a breadth of scanning capabilities. Don't leak secrets, scan every commit and ensure secrets don't make it to production. Protect the privileged CI/CD environment from malicious activity that could result in access to source code, secrets, and more. Run with registry rules or your own. Code is analyzed locally (not uploaded). Get results at ludicrous speed with diff-aware scans, review findings in MR and PR comments, and deploy Semgrep across your organization’s projects. Go beyond the registry with rules specific to your organization. Write rules to enforce your own code guardrails.

DPRLE (decision procedure for regular language equations) solves subset constraints that involve language variables and concatenation.

Flow is a static type checker for JavaScript. It was designed to help improve code quality and developer productivity. It does this through several smart capabilities. First, it identifies problems as you code, so you no longer have to waste time guessing and checking again and again. Second, it understands your code and makes its knowledge available, allowing you to build other smart tools on top of it. Third, it helps you refactor safely so you can focus on the changes you want to make and not on what you might break. Lastly, it can help prevent bad rebases and protect your carefully designed library, which is especially relevant when working with a large group of developers. Flow integrates with many tools, so you can easily and seamlessly insert it into your existing workflow and toolchain.

ParTools allows the interactive analysis of a C program execution profile and data dependencies to facilitate the discovery and selection of suitable parallelization candidates in a manual parallelization process. The flow does not assume any specific parallelization technique, thus it can be broadly applied. The original (serial) C source is automatically annotated to trace the execution profile and data dependencies at run-time. The annotated program is then executed using a significant (but small) data set selected by the developer. The data collected is cross-referenced with the original source and can be interactively analyzed graphically to determine the best parallelization candidates and techniques.