Is accept_values_for safe to use?

accept_values_for has no known vulnerabilities on the latest version (0.9.6). DepScope rates its health at 50/100 (high risk).

What is the latest version of accept_values_for?

The latest version of accept_values_for is 0.9.6, released 2025-10-22.

Does accept_values_for have known vulnerabilities?

No known vulnerabilities on the latest version of accept_values_for.

Is accept_values_for deprecated?

No, accept_values_for is actively maintained. Latest release: 0.9.6 (2025-10-22).

What are alternatives to accept_values_for?

Popular alternatives to accept_values_for in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does accept_values_for use?

accept_values_for is licensed under MIT.

accept_values_for

rubygemsv0.9.6

Writing specs for complex validations is annoying. AcceptValuesFor makes iteasy to test your validations with real world values, asserting which valuesshould be accepted by your model and which should not.

License MITpermissive20 versions2 deps2,686 weekly dl

bogdan/accept_values_for

/ 100

Health

safe to use

[email protected] is safe to use (health: 50/100)

Health breakdown0 – 100

10/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

activemodel rspec

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/accept_values_for