Is bounce_email safe to use?

bounce_email has no known vulnerabilities on the latest version (0.2.8). DepScope rates its health at 45/100 (high risk).

What is the latest version of bounce_email?

The latest version of bounce_email is 0.2.8, released 2017-07-01.

Does bounce_email have known vulnerabilities?

No known vulnerabilities on the latest version of bounce_email.

Is bounce_email deprecated?

No, bounce_email is actively maintained. Latest release: 0.2.8 (2017-07-01).

What are alternatives to bounce_email?

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

What license does bounce_email use?

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

bounce_email

rubygemsv0.2.8

fork of whatcould/bounce-email incl. patches from wakiki, peterpunk, agowan & rngtng

9 versions1 deps276,792 weekly dl

http://github.com/mitio/bounce_email

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

mail

API access

Get this data programmatically — free, no authentication.

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