Is ansible-lint-to-junit-xml safe to use?

ansible-lint-to-junit-xml has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 30/100 (critical risk).

What is the latest version of ansible-lint-to-junit-xml?

The latest version of ansible-lint-to-junit-xml is 0.1.0, released 2019-07-31.

Does ansible-lint-to-junit-xml have known vulnerabilities?

No known vulnerabilities on the latest version of ansible-lint-to-junit-xml.

Is ansible-lint-to-junit-xml deprecated?

No, ansible-lint-to-junit-xml is actively maintained. Latest release: 0.1.0 (2019-07-31).

What are alternatives to ansible-lint-to-junit-xml?

Popular alternatives to ansible-lint-to-junit-xml in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does ansible-lint-to-junit-xml use?

ansible-lint-to-junit-xml is licensed under MIT.

ansible-lint-to-junit-xml

pypiv0.1.0

Convert ansible-lint outputs to a jUnit valid xml tests result file

License MITpermissive1 versions1 maintainers0 deps250 weekly dl

andreferreirav2/ansible-lint-to-junit-xml

/ 100

Health

use with caution

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

Moderate health score (30/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

0/15

maturity

2/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/pypi/ansible-lint-to-junit-xml