Is lockfile-subset safe to use?

lockfile-subset has no known vulnerabilities on the latest version (1.2.1). DepScope rates its health at 53/100 (high risk).

What is the latest version of lockfile-subset?

The latest version of lockfile-subset is 1.2.1, released 2026-03-22.

Does lockfile-subset have known vulnerabilities?

No known vulnerabilities on the latest version of lockfile-subset.

Is lockfile-subset deprecated?

No, lockfile-subset is actively maintained. Latest release: 1.2.1 (2026-03-22).

What are alternatives to lockfile-subset?

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

What license does lockfile-subset use?

lockfile-subset is licensed under MIT.

lockfile-subset

npmv1.2.1

Extract a subset of package-lock.json, pnpm-lock.yaml, or yarn.lock for specified packages and their transitive dependencies

License MITpermissive6 versions1 maintainers3 deps

tmokmss/lockfile-subset

/ 100

Health

use with caution

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

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (3)

@npmcli/arborist @yarnpkg/lockfile js-yaml

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/lockfile-subset