Brakeman vs Microsoft DevSkim
Brakeman
brakemanscanner.orgMicrosoft DevSkim
github.comSide by side
| Figure | Brakeman | Microsoft DevSkim |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Static Application Security Testing Software | 7.9 (#11) | 7.9 (#12) |
| Purpose | Brakeman is a static analysis scanner that checks Ruby on Rails application code for potential security vulnerabilities. | DevSkim provides IDE plugins, language analyzers, and rules for security linting and static source-code analysis. |
| Support | The project links users to GitHub Discussions and Issues for community questions and bug reports. | Support is limited to GitHub issues and the project wiki resources listed in its support policy. |
Plans
In their own words
Brakeman
Brakeman has no write-up on Specifiction yet; its figures are above.
Microsoft DevSkim
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.