
Security News
Static vs. Runtime Reachability: Insights from Latio’s On the Record Podcast
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.
Ruby library to validate hashes (Hash) against user-defined requirements
Add this line to your application's Gemfile:
gem 'hash_validator'
And then execute:
$ bundle
Or install it yourself as:
$ gem install hash_validator
# Validations hash
validations = {
user: {
first_name: String,
last_name: 'string',
age: 'numeric',
likes: 'array'
}
}
# Hash to validate
hash = {
foo: 1,
bar: 'baz',
user: {
first_name: 'James',
last_name: 12345
}
}
validator = HashValidator.validate(hash, validations)
validator.valid?
# => false
validator.errors
# {
:user => {
:last_name => "string required",
:age => "numeric required",
:likes => "array required"
}
}
Define a validation hash which will be used to validate. This has can be nested as deeply as required using the following values to validate specific value types:
array
boolean
complex
enumerable
float
integer
numeric
range
rational
regexp
string
symbol
time
required
: just requires any value to be present for the designated key.{}
can be used.On top of the pre-defined simple types, classes can be used directly (e.g. String) to validate the presence of a value of a desired class.
Additional validations exist to validate beyond simple typing, such as:
email
: email address validation (string + email address).Example use-cases include Ruby APIs (I'm currently using it in a Rails API that I'm building for better error responses to developers).
Allows custom defined validations (must inherit from HashValidator::Validator::Base
). Example:
# Define our custom validator
class HashValidator::Validator::OddValidator < HashValidator::Validator::Base
def initialize
super('odd') # The name of the validator
end
def validate(key, value, validations, errors)
unless value.is_a?(Integer) && value.odd?
errors[key] = presence_error_message
end
end
end
# Add the validator
HashValidator.append_validator(HashValidator::Validator::OddValidator.new)
# Now the validator can be used! e.g.
validator = HashValidator.validate({ age: 27 }, { age: 'odd' })
validator.valid? # => true
validator.errors # => {}
Multiple validators can be applied to a single key, e.g.
HashValidator.validate(
{ foo: 73 },
{ foo: HashValidator.multiple('numeric', 1..100) }
)
This is particularly useful when defining custom validators.
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)git push origin my-new-feature
)FAQs
Unknown package
We found that hash_validator demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.
Security News
The latest Opengrep releases add Apex scanning, precision rule tuning, and performance gains for open source static code analysis.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.