Is test-unit-context safe to use?

test-unit-context has no known vulnerabilities on the latest version (0.5.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of test-unit-context?

The latest version of test-unit-context is 0.5.1, released 2016-02-01.

Does test-unit-context have known vulnerabilities?

No known vulnerabilities on the latest version of test-unit-context.

Is test-unit-context deprecated?

No, test-unit-context is actively maintained. Latest release: 0.5.1 (2016-02-01).

What are alternatives to test-unit-context?

Popular alternatives to test-unit-context in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does test-unit-context use?

test-unit-context is licensed under Apache-2.0.

test-unit-context

rubygemsv0.5.1

Makes Test::Unit::TestCases 'contextable' and thus much easier to read and write. If you've seen RSpec than it's the very same 'context do ... end' re-invendet for Test::Unit. Inspired by gem 'context' that does a similar job for the 'old' Test::Unit bundled with Ruby 1.8.x standard libraries.

License Apache-2.0permissive7 versions1 deps284,307 weekly dl

kares/test-unit-context

/ 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)

test-unit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/test-unit-context