Is cert_validator safe to use?

cert_validator has no known vulnerabilities on the latest version (0.0.1). DepScope rates its health at 39/100 (critical risk).

What is the latest version of cert_validator?

The latest version of cert_validator is 0.0.1, released 2014-08-19.

Does cert_validator have known vulnerabilities?

No known vulnerabilities on the latest version of cert_validator.

Is cert_validator deprecated?

No, cert_validator is actively maintained. Latest release: 0.0.1 (2014-08-19).

What are alternatives to cert_validator?

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

What license does cert_validator use?

cert_validator is licensed under MIT.

cert_validator

rubygemsv0.0.1

Validate an X509 certificate against its listed OCSP endpoint and/or a CRL.

License MITpermissive1 versions0 deps178,453 weekly dl

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

0/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/cert_validator

cert_validator

rubygemsv0.0.1

Validate an X509 certificate against its listed OCSP endpoint and/or a CRL.

License MITpermissive1 versions0 deps178,453 weekly dl

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

0/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/cert_validator