Is openssl-signature_algorithm safe to use?

openssl-signature_algorithm has no known vulnerabilities on the latest version (1.3.0). DepScope rates its health at 51/100 (high risk).

What is the latest version of openssl-signature_algorithm?

The latest version of openssl-signature_algorithm is 1.3.0, released 2023-02-15.

Does openssl-signature_algorithm have known vulnerabilities?

No known vulnerabilities on the latest version of openssl-signature_algorithm.

Is openssl-signature_algorithm deprecated?

No, openssl-signature_algorithm is actively maintained. Latest release: 1.3.0 (2023-02-15).

What are alternatives to openssl-signature_algorithm?

Popular alternatives to openssl-signature_algorithm in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does openssl-signature_algorithm use?

openssl-signature_algorithm is licensed under Apache-2.0.

openssl-signature_algorithm

rubygemsv1.3.0

ECDSA, EdDSA, RSA-PSS and RSA-PKCS#1 algorithms for ruby

License Apache-2.0permissive10 versions1 deps24,571,994 weekly dl

cedarcode/openssl-signature_algorithm

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.49medium

Download trend

stable(0%)

Health History

Dependency Tree

License Audit

Dependencies (1)

openssl

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/openssl-signature_algorithm