Is le-challenge-dns safe to use?

le-challenge-dns has no known vulnerabilities on the latest version (3.0.7). DepScope rates its health at 9/100 (critical risk).

What is the latest version of le-challenge-dns?

The latest version of le-challenge-dns is 3.0.7, released 2019-05-16.

Does le-challenge-dns have known vulnerabilities?

No known vulnerabilities on the latest version of le-challenge-dns.

Is le-challenge-dns deprecated?

Yes, le-challenge-dns is deprecated: Please use acme-dns-01-cli. See https://www.npmjs.com/package/acme-dns-01-cli Consider using semver instead.

What are alternatives to le-challenge-dns?

Popular alternatives to le-challenge-dns in npm include: semver, minimatch, ansi-styles, debug, brace-expansion.

What license does le-challenge-dns use?

le-challenge-dns is licensed under MPL-2.0.

le-challenge-dns

npmv3.0.7deprecated

A manual (interactive CLI) dns-based strategy for Greenlock / Let's Encrypt / ACME DNS-01 challenges

License MPL-2.0weak copyleft13 versions1 maintainers0 deps32 weekly dl

https://git.rootprojects.org/root/acme-dns-01-cli.js

/ 100

Health

find alternative

le-challenge-dns is deprecated — find an alternative

Moderate health score (9/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

2.4 KBminified

1.0 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/le-challenge-dns