Is puppet-lint-legacy_facts-check safe to use?

puppet-lint-legacy_facts-check has no known vulnerabilities on the latest version (1.0.4). DepScope rates its health at 49/100 (high risk).

What is the latest version of puppet-lint-legacy_facts-check?

The latest version of puppet-lint-legacy_facts-check is 1.0.4, released 2020-04-04.

Does puppet-lint-legacy_facts-check have known vulnerabilities?

No known vulnerabilities on the latest version of puppet-lint-legacy_facts-check.

Is puppet-lint-legacy_facts-check deprecated?

No, puppet-lint-legacy_facts-check is actively maintained. Latest release: 1.0.4 (2020-04-04).

What are alternatives to puppet-lint-legacy_facts-check?

Popular alternatives to puppet-lint-legacy_facts-check in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does puppet-lint-legacy_facts-check use?

puppet-lint-legacy_facts-check is licensed under Apache-2.0.

puppet-lint-legacy_facts-check

rubygemsv1.0.4

A pupet-lint to check you are not using legacy facts like `$::operatingsystem` or `$facts['operatingsystem']`. You should use the new structured facts like `$facts['os']['name']` instead

License Apache-2.0permissive11 versions1 deps701,858 weekly dl

mmckinst/puppet-lint-legacy_facts-check

/ 100

Health

use with caution

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

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

1/15

community

0/15

popularity_floor

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

puppet-lint

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/puppet-lint-legacy_facts-check