Is rfc-822 safe to use?

rfc-822 has no known vulnerabilities on the latest version (0.4.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of rfc-822?

The latest version of rfc-822 is 0.4.1, released 2015-12-08.

Does rfc-822 have known vulnerabilities?

No known vulnerabilities on the latest version of rfc-822.

Is rfc-822 deprecated?

No, rfc-822 is actively maintained. Latest release: 0.4.1 (2015-12-08).

What are alternatives to rfc-822?

Popular alternatives to rfc-822 in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does rfc-822 use?

License information for rfc-822 is not declared in the registry metadata.

rfc-822

rubygemsv0.4.1

RFC822 compatible email validation and MX record check

6 versions0 deps293,920 weekly dl

http://github.com/dim/rfc-822

/ 100

Health

use with caution

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

Moderate health score (45/100) — verify manually

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

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/rfc-822