Is package-lock-sanitizer safe to use?

package-lock-sanitizer has no known vulnerabilities on the latest version (1.0.4). DepScope rates its health at 42/100 (high risk).

What is the latest version of package-lock-sanitizer?

The latest version of package-lock-sanitizer is 1.0.4, released 2023-09-15.

Does package-lock-sanitizer have known vulnerabilities?

No known vulnerabilities on the latest version of package-lock-sanitizer.

Is package-lock-sanitizer deprecated?

No, package-lock-sanitizer is actively maintained. Latest release: 1.0.4 (2023-09-15).

What are alternatives to package-lock-sanitizer?

Popular alternatives to package-lock-sanitizer in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does package-lock-sanitizer use?

package-lock-sanitizer is licensed under Apache-2.0.

package-lock-sanitizer

npmv1.0.4

A script that resets the resolves registry URLs in package lock to the official NPM registry.

License Apache-2.0permissive5 versions1 maintainers6 deps805 weekly dl

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (6)

@oclif/command @oclif/config @oclif/errors @oclif/plugin-help fs replace-in-file

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/package-lock-sanitizer