Puma Scan vs Pysa

Puma Scan is a static application security testing tool for C# code in Visual Studio. Its End User Edition scans code as developers write and reports vulnerabilities as compiler warnings before a commit. The extension supports C# in.NET Framework and.NET Core, including Web Forms and MVC; legacy website projects are unsupported. The product page says it also scans AI-generated code from GitHub Copilot, Cursor, Claude, ChatGPT, Amazon Q and Gemini Code Assist. For automated scanning, listed integrations include GitHub Actions, GitLab CI and Azure DevOps. CI editions can enforce configurable vulnerability severity thresholds and stop builds when requirements are not met. The Server Edition supports command-line scans, on-premises Azure DevOps build tasks and exports in HTML, JSON, MSBuild, VSO, VSTest and CSV formats. Community is free. End User costs $299 a year; Server is $4,999 a year, Cloud CI Standard $5,999 a year and Cloud CI Unlimited $10,999 a year. Trials last 30 days, require no credit card and do not include reporting. Community analyzers run locally and do not contact Puma Scan servers for rule updates.

Pysa is a free, open-source Python static analysis tool that uses taint analysis to identify potential security issues. It follows data from configured sources toward dangerous sinks, such as user-controlled request data reaching an eval call. Users configure sources, sinks, features and rules in taint.config, and annotate code with .pysa model files; built-in and common Python libraries have prewritten models and rules. Sanitizer models describe data that should lose taint, including function parameters and return values. Pysa analyzes the target repository and directories in the configured search_path, but not dependency source outside that scope. When it cannot access a function’s source, it assumes the return value retains taint, which can lead to false positives. Analysis may freeze on similarly sized projects if the machine lacks enough memory. The quickstart installs it with pip install pyre-check in a Python virtual environment. Pyre supports the Language Server Protocol, and a VSCode extension connects to a running server. SAPP can ingest results for viewing and filtering in a local web UI; a GitHub Action can run Pysa in CI and show findings in GitHub’s Security code scanning UI. Pysa requires Python 3.9 or later and relies on type information from Pyrefly. The project says it can analyze codebases with millions of lines. Its repository is MIT-licensed; the Pyre repository was archived on June 26, 2026, and says Pysa moved to its own repository.