Reek vs Snyk

Overview

Snyk

Stacks580

Followers380

Votes20

Reek

Stacks9

Followers22

Votes0

GitHub Stars4.1K

Forks282

Reek vs Snyk: What are the differences?

Focus of Analysis: Reek primarily analyzes code to detect and report code smells, which are indicators of design weaknesses that may lead to issues in the future. On the other hand, Snyk focuses on identifying security vulnerabilities within the codebase by analyzing dependencies for known vulnerabilities and providing remediation suggestions.
Types of Issues Detected: Reek mainly identifies issues related to code quality, duplication, complexity, and other design-related concerns. In contrast, Snyk specifically looks for security vulnerabilities such as outdated libraries, known security issues in dependencies, and potential exploit risks that could compromise the application's security.
Integration with Development Workflow: Reek is often integrated into the development process and used by developers during coding and code review stages to improve code quality and maintainability. In contrast, Snyk is commonly integrated into the continuous integration/continuous deployment (CI/CD) pipeline to automate security checks and ensure that vulnerabilities are detected as early as possible in the development lifecycle.
Language Support: Reek is primarily focused on Ruby code analysis and provides specific rules tailored to the Ruby programming language. Meanwhile, Snyk supports multiple programming languages including JavaScript, Java, Python, Ruby, and more, making it a versatile choice for projects using different tech stacks.
Remediation Guidance: While Reek reports code smells and design issues, it may not provide detailed guidance on how to address them. On the other hand, Snyk not only identifies security vulnerabilities but also offers actionable remediation advice, including patching dependencies, upgrading libraries, and configuration changes to mitigate the risks.
Community Support and Updates: Reek has a smaller community compared to Snyk and may have fewer updates and new features released regularly. Snyk, with a larger user base, receives more frequent updates, improvements, and additions to its vulnerability database, ensuring better coverage and accuracy in detecting security issues.

In Summary, Reek focuses on code smell detection and design issues in Ruby code, while Snyk specializes in security vulnerability detection across multiple programming languages, providing actionable remediation guidance and integration with the CI/CD pipeline to ensure early detection and mitigation of security risks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Snyk, Reek

Bryan

SRE Manager at Subsplash

Apr 1, 2020

Needs adviceon

WhiteSource

Snyk

Sonatype Nexus

I'm beginning to research the right way to better integrate how we achieve SCA / shift-left / SecureDevOps / secure software supply chain. If you use or have evaluated WhiteSource, Snyk, Sonatype Nexus, SonarQube or similar, I would very much appreciate your perspective on strengths and weaknesses and how you selected your ultimate solution. I want to integrate with GitLab CI.

461k views461k

Comments

Detailed Comparison

Snyk	Reek
Automatically find & fix vulnerabilities in your code, containers, Kubernetes, and Terraform	Reek is a tool that examines Ruby classes, modules, and methods and reports any Code Smells it finds.
Statistics
GitHub Stars -	GitHub Stars 4.1K
GitHub Forks -	GitHub Forks 282
Stacks 580	Stacks 9
Followers 380	Followers 22
Votes 20	Votes 0
Pros & Cons
Pros 10 Github Integration 5 Free for open source projects 4 Finds lots of real vulnerabilities 1 Easy to deployed Cons 2 Does not integrated with SonarQube 1 False positives 1 Complex UI 1 No surface monitoring 1 No malware detection	No community feedback yet
Integrations
Scala .NET GitHub CircleCI Docker JavaScript Node.js Python Golang Java	Atom Sublime Text Vim TextMate Emacs

What are some alternatives to Snyk, Reek?

Code Climate

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

PullReview

PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.

Gerrit Code Review

Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

SonarQube

SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.

RuboCop

RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.

CodeFactor.io

CodeFactor.io automatically and continuously tracks code quality with every GitHub or BitBucket commit and pull request, helping software developers save time in code reviews and efficiently tackle technical debt.

ESLint

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Amazon CodeGuru

It is a machine learning service for automated code reviews and application performance recommendations. It helps you find the most expensive lines of code that hurt application performance and keep you up all night troubleshooting, then gives you specific recommendations to fix or improve your code.

Related Comparisons

Reek vs Snyk: What are the differences?

Focus of Analysis: Reek primarily analyzes code to detect and report code smells, which are indicators of design weaknesses that may lead to issues in the future. On the other hand, Snyk focuses on identifying security vulnerabilities within the codebase by analyzing dependencies for known vulnerabilities and providing remediation suggestions.
Types of Issues Detected: Reek mainly identifies issues related to code quality, duplication, complexity, and other design-related concerns. In contrast, Snyk specifically looks for security vulnerabilities such as outdated libraries, known security issues in dependencies, and potential exploit risks that could compromise the application's security.
Integration with Development Workflow: Reek is often integrated into the development process and used by developers during coding and code review stages to improve code quality and maintainability. In contrast, Snyk is commonly integrated into the continuous integration/continuous deployment (CI/CD) pipeline to automate security checks and ensure that vulnerabilities are detected as early as possible in the development lifecycle.
Language Support: Reek is primarily focused on Ruby code analysis and provides specific rules tailored to the Ruby programming language. Meanwhile, Snyk supports multiple programming languages including JavaScript, Java, Python, Ruby, and more, making it a versatile choice for projects using different tech stacks.
Remediation Guidance: While Reek reports code smells and design issues, it may not provide detailed guidance on how to address them. On the other hand, Snyk not only identifies security vulnerabilities but also offers actionable remediation advice, including patching dependencies, upgrading libraries, and configuration changes to mitigate the risks.
Community Support and Updates: Reek has a smaller community compared to Snyk and may have fewer updates and new features released regularly. Snyk, with a larger user base, receives more frequent updates, improvements, and additions to its vulnerability database, ensuring better coverage and accuracy in detecting security issues.

Reek vs Snyk

Overview