Horusec vs Microsoft DevSkim

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.

Microsoft DevSkim is a free, MIT-licensed toolkit for security linting and static source-code analysis. It provides IDE extensions, language analyzers, and rules to help developers identify and address security vulnerabilities early. It includes built-in rules and allows teams to write their own using JSONPath, XPath, and YmlPath. Listed language support includes C, C++, C#, Cobol, Go, Java, JavaScript/TypeScript, and Python, among others. Its cross-platform .NET CLI analyzes files and directories and can be installed as a global tool or obtained as binaries for Windows, macOS, and Linux. A C# library is also available for embedding analysis in other tools. Results can be emitted as SARIF, JSON, or text; the CLI can apply suggested fixes from SARIF results and add suppression comments. The project lists extensions for Visual Studio Code and Visual Studio, and supports CI/CD in self-hosted environments. Support is limited to GitHub issues and project wiki resources. Vulnerability reports should be sent privately to Microsoft's Security Response Center rather than posted publicly.