Is exceptional_synchrony safe to use?

exceptional_synchrony has no known vulnerabilities on the latest version (1.4.6). DepScope rates its health at 49/100 (high risk).

What is the latest version of exceptional_synchrony?

The latest version of exceptional_synchrony is 1.4.6, released 2024-07-15.

Does exceptional_synchrony have known vulnerabilities?

No known vulnerabilities on the latest version of exceptional_synchrony.

Is exceptional_synchrony deprecated?

No, exceptional_synchrony is actively maintained. Latest release: 1.4.6 (2024-07-15).

What are alternatives to exceptional_synchrony?

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

What license does exceptional_synchrony use?

exceptional_synchrony is licensed under MIT.

exceptional_synchrony

rubygemsv1.4.6

Extensions to EventMachine/Synchrony to work well with exceptions

License MITpermissive19 versions5 deps10,672 weekly dl

Invoca/exceptional_synchrony

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (5)

em-http-request em-synchrony eventmachine exception_handling invoca-utils

API access

Get this data programmatically — free, no authentication.

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