Is semaphore_cucumber_booster_config safe to use?

semaphore_cucumber_booster_config has no known vulnerabilities on the latest version (1.4.2). DepScope rates its health at 55/100 (high risk).

What is the latest version of semaphore_cucumber_booster_config?

The latest version of semaphore_cucumber_booster_config is 1.4.2, released 2021-08-06.

Does semaphore_cucumber_booster_config have known vulnerabilities?

No known vulnerabilities on the latest version of semaphore_cucumber_booster_config.

Is semaphore_cucumber_booster_config deprecated?

No, semaphore_cucumber_booster_config is actively maintained. Latest release: 1.4.2 (2021-08-06).

What are alternatives to semaphore_cucumber_booster_config?

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

What license does semaphore_cucumber_booster_config use?

License information for semaphore_cucumber_booster_config is not declared in the registry metadata.

semaphore_cucumber_booster_config

rubygemsv1.4.2

Injects additional configuration for Cucumber so that it outputs JSON suitable for auto-parallelism without affecting stdout.

14 versions1 deps5,450,275 weekly dl

renderedtext/cucumber_booster_config

/ 100

Health

use with caution

[email protected] low health (55/100) — consider alternatives

Moderate health score (55/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

0/15

community

4/15

popularity_floor

Vulnerabilities

none known

Quality signals

OSS Criticality

0.45medium

Health History

Dependency Tree

License Audit

Dependencies (1)

thor

API access

Get this data programmatically — free, no authentication.

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