decafsucks VS dry-validation

Compare decafsucks vs dry-validation and see what are their differences.


Rebuilding as an OSS Hanami 2.0 example app (by decafsucks)
Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
decafsucks dry-validation
1 3
51 1,268
- 0.6%
10.0 4.7
about 1 month ago 18 days ago
Ruby Ruby
- MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of decafsucks. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning decafsucks yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of dry-validation. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-02.
  • Leveraging complexity of service objects with dry libraries
    3 projects | | 2 Sep 2021
    ➡️ First, we need to upgrade the validation process. For this will be used the gem dry-validation. It adds validations that are expressed through contract objects.
    3 projects | | 2 Sep 2021
    ➡️ The most interesting part is the ConductResearchContract. It validates each element of the experiments array for compliance with the schema defined in the ConductExperimentContract. Sadly, now, to run rules for each experiment, you must run them manually like in the rule(:experiments).
  • How to express this data type in Ruby?
    2 projects | | 13 Feb 2021
    I wouldn't add any type validations in my first version. Should they be needed I would use

What are some alternatives?

When comparing decafsucks and dry-validation you can also consider the following projects:

Ruby JSON Schema Validator - Ruby JSON Schema Validator

rbs - Type Signature for Ruby


rails_or - Cleaner syntax for writing OR Query in Rails 5, 6. And also add #or support to Rails 3 and 4.

activerecord_json_validator - 🔩 ActiveRecord::JSONValidator makes it easy to validate JSON attributes against a JSON schema.

Ryakuzu - :heart_eyes_cat: Interface for schema.rb

FindWithOrder - Provides a simple way to find records in the same order of input array. Has better performance than manually sorting. (Support both PostgreSQL and MySQL)

ValidatesZipcode - Postal code / zipcode validation for Rails, supporting 233 country codes

ActiveRecordExtended - Adds additional postgres functionality to an ActiveRecord / Rails application

dry-struct - Typed struct and value objects

dry-core - A toolset of small support modules used throughout the @dry-rb & @rom-rb ecosystems

modular_routes - Dedicated controllers for each of your Rails route actions.