Horusec vs Pysa

Horusec is a static code analysis tool for identifying security flaws during development. It scans source code and searches project files and Git history for leaked keys and other security issues. The project describes analyzing 18 languages with 20 security tools; listed coverage includes C#, Java, Kotlin, Python, Ruby, Golang, Terraform, JavaScript, TypeScript, Kubernetes, PHP, C, HTML, JSON, Dart, Elixir, Shell, and Nginx. Analysis is configurable through CLI resources. Developers can use its command-line interface, while DevSecOps teams can add it to CI/CD pipelines; a Visual Studio Code extension is also provided. Horusec-Web offers vulnerability dashboards, false-positive controls, authorization tokens, and vulnerability updates. Horusec Platform integrates with the CLI to visualize and manage vulnerabilities, and supports native Horusec, LDAP, and Keycloak authentication. Its repository was archived by its owner on March 19, 2025 and is read-only. Running Horusec with all its tools requires Docker; the platform requires RabbitMQ and PostgreSQL. The open-source plan is free under Apache License 2.0.

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.