Is @segment/legacy-each safe to use?

@segment/legacy-each has no known vulnerabilities on the latest version (2.0.1-rc.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of @segment/legacy-each?

The latest version of @segment/legacy-each is 2.0.1-rc.0, released 2020-07-15.

Does @segment/legacy-each have known vulnerabilities?

No known vulnerabilities on the latest version of @segment/legacy-each.

Is @segment/legacy-each deprecated?

No, @segment/legacy-each is actively maintained. Latest release: 2.0.1-rc.0 (2020-07-15).

What are alternatives to @segment/legacy-each?

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

What license does @segment/legacy-each use?

@segment/legacy-each is licensed under MIT.

@segment/legacy-each

npmv2.0.1-rc.0

Iterate over a collection, invoking a function for each element.

License MITpermissive1 versions339 maintainers1 deps

segmentio/legacy-javascript-utils

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@segment/legacy-keys

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@segment/legacy-each