Is elegant-status safe to use?

elegant-status has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of elegant-status?

The latest version of elegant-status is 1.1.0, released 2016-05-20.

Does elegant-status have known vulnerabilities?

No known vulnerabilities on the latest version of elegant-status.

Is elegant-status deprecated?

No, elegant-status is actively maintained. Latest release: 1.1.0 (2016-05-20).

What are alternatives to elegant-status?

Popular alternatives to elegant-status in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does elegant-status use?

elegant-status is licensed under MIT.

elegant-status

npmv1.1.0

Create elegant task status for CLI.

License MITpermissive2 versions1 maintainers4 deps

inikulin/elegant-status

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

chalk elegant-spinner log-update os-family

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/elegant-status