Is combined_time_select safe to use?

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

What is the latest version of combined_time_select?

The latest version of combined_time_select is 2.0.0, released 2017-08-09.

Does combined_time_select have known vulnerabilities?

No known vulnerabilities on the latest version of combined_time_select.

Is combined_time_select deprecated?

No, combined_time_select is actively maintained. Latest release: 2.0.0 (2017-08-09).

What are alternatives to combined_time_select?

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

What license does combined_time_select use?

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

combined_time_select

rubygemsv2.0.0

Generates a time_select field like Google calendar.

4 versions1 deps914,081 weekly dl

http://github.com/excid3/combined_time_select

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

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

Dependencies (1)

rails

API access

Get this data programmatically — free, no authentication.

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