Is be_valid_asset safe to use?

be_valid_asset has no known vulnerabilities on the latest version (1.3.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of be_valid_asset?

The latest version of be_valid_asset is 1.3.1, released 2016-07-26.

Does be_valid_asset have known vulnerabilities?

No known vulnerabilities on the latest version of be_valid_asset.

Is be_valid_asset deprecated?

No, be_valid_asset is actively maintained. Latest release: 1.3.1 (2016-07-26).

What are alternatives to be_valid_asset?

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

What license does be_valid_asset use?

be_valid_asset is licensed under MIT.

be_valid_asset

rubygemsv1.3.1

Provides be_valid_markup, be_valid_css and be_valid_feed matchers for RSpec controller and view tests.

License MITpermissive8 versions1 deps185,345 weekly dl

http://github.com/unboxed/be_valid_asset

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

rspec

API access

Get this data programmatically — free, no authentication.

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