Is secure_yaml safe to use?

secure_yaml has no known vulnerabilities on the latest version (2.0.2). DepScope rates its health at 48/100 (high risk).

What is the latest version of secure_yaml?

The latest version of secure_yaml is 2.0.2, released 2017-02-09.

Does secure_yaml have known vulnerabilities?

No known vulnerabilities on the latest version of secure_yaml.

Is secure_yaml deprecated?

No, secure_yaml is actively maintained. Latest release: 2.0.2 (2017-02-09).

What are alternatives to secure_yaml?

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

What license does secure_yaml use?

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

secure_yaml

rubygemsv2.0.2

encryption protection for sensitive yaml properties

9 versions0 deps5,839,670 weekly dl

qmg-hlewis/secure_yaml

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.45medium

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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