Is ansible-lint-custom-strict-naming safe to use?

ansible-lint-custom-strict-naming has no known vulnerabilities on the latest version (1.1.2). DepScope rates its health at 31/100 (critical risk).

What is the latest version of ansible-lint-custom-strict-naming?

The latest version of ansible-lint-custom-strict-naming is 1.1.2, released 2024-09-13.

Does ansible-lint-custom-strict-naming have known vulnerabilities?

No known vulnerabilities on the latest version of ansible-lint-custom-strict-naming.

Is ansible-lint-custom-strict-naming deprecated?

No, ansible-lint-custom-strict-naming is actively maintained. Latest release: 1.1.2 (2024-09-13).

What are alternatives to ansible-lint-custom-strict-naming?

Popular alternatives to ansible-lint-custom-strict-naming in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does ansible-lint-custom-strict-naming use?

License information for ansible-lint-custom-strict-naming is not declared in the registry metadata.

ansible-lint-custom-strict-naming

pypiv1.1.2

Add your description here

10 versions1 deps20 weekly dl

pollenjp/ansible-lint-custom-strict-naming

/ 100

Health

use with caution

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

Moderate health score (31/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

ansible-lint

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/ansible-lint-custom-strict-naming