Is @pm2/legacy-tracing safe to use?

@pm2/legacy-tracing has no known vulnerabilities on the latest version (1.4.2). DepScope rates its health at 43/100 (high risk).

What is the latest version of @pm2/legacy-tracing?

The latest version of @pm2/legacy-tracing is 1.4.2, released 2018-12-05.

Does @pm2/legacy-tracing have known vulnerabilities?

No known vulnerabilities on the latest version of @pm2/legacy-tracing.

Is @pm2/legacy-tracing deprecated?

No, @pm2/legacy-tracing is actively maintained. Latest release: 1.4.2 (2018-12-05).

What are alternatives to @pm2/legacy-tracing?

Popular alternatives to @pm2/legacy-tracing in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @pm2/legacy-tracing use?

@pm2/legacy-tracing is licensed under Apache-2.0.

@pm2/legacy-tracing

npmv1.4.2

Node.js Tracing Driver

License Apache-2.0permissive3 versions2 maintainers11 deps478 weekly dl

/ 100

Health

use with caution

@pm2/[email protected] low health (43/100) — consider alternatives

Moderate health score (43/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (11)

@pm2/continuation-local-storage debug extend is lodash.findindex lodash.isequal lodash.merge methods semver shimmer uuid

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pm2/legacy-tracing