Is @pnpm/registry.pkg-metadata-filter safe to use?

@pnpm/registry.pkg-metadata-filter has no known vulnerabilities on the latest version (1000.1.6). DepScope rates its health at 59/100 (high risk).

What is the latest version of @pnpm/registry.pkg-metadata-filter?

The latest version of @pnpm/registry.pkg-metadata-filter is 1000.1.6, released 2026-01-19.

Does @pnpm/registry.pkg-metadata-filter have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/registry.pkg-metadata-filter.

Is @pnpm/registry.pkg-metadata-filter deprecated?

No, @pnpm/registry.pkg-metadata-filter is actively maintained. Latest release: 1000.1.6 (2026-01-19).

What are alternatives to @pnpm/registry.pkg-metadata-filter?

Popular alternatives to @pnpm/registry.pkg-metadata-filter in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @pnpm/registry.pkg-metadata-filter use?

@pnpm/registry.pkg-metadata-filter is licensed under MIT.

@pnpm/registry.pkg-metadata-filter

npmv1000.1.6

Filters the package metadata from the registry

License MITpermissive8 versions2 maintainers2 deps47,624 weekly dl

pnpm/pnpm.git#main

/ 100

Health

use with caution

@pnpm/[email protected] low health (59/100) — consider alternatives

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

semver @pnpm/registry.types

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/registry.pkg-metadata-filter