Is should_not safe to use?

should_not has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of should_not?

The latest version of should_not is 1.1.0, released 2014-10-01.

Does should_not have known vulnerabilities?

No known vulnerabilities on the latest version of should_not.

Is should_not deprecated?

No, should_not is actively maintained. Latest release: 1.1.0 (2014-10-01).

What are alternatives to should_not?

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

What license does should_not use?

should_not is licensed under MIT.

should_not

rubygemsv1.1.0

You should_not start your specs with the string "should". If every spec starts with "should", then it's redundant everywhere. Instead, write in an active tone: `it "should ignore nil elements"` - BAD `it "ignores nil elements"` - GOOD

License MITpermissive4 versions0 deps469,526 weekly dl

should-not/should_not

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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