Is @pnpm/config.env-replace safe to use?

@pnpm/config.env-replace has no known vulnerabilities on the latest version (4.1.0). DepScope rates its health at 69/100 (moderate risk).

What is the latest version of @pnpm/config.env-replace?

The latest version of @pnpm/config.env-replace is 4.1.0, released 2026-05-15.

Does @pnpm/config.env-replace have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/config.env-replace.

Is @pnpm/config.env-replace deprecated?

No, @pnpm/config.env-replace is actively maintained. Latest release: 4.1.0 (2026-05-15).

What are alternatives to @pnpm/config.env-replace?

Popular alternatives to @pnpm/config.env-replace in npm include: ?, semver, debug, ansi-styles, minimatch.

What license does @pnpm/config.env-replace use?

@pnpm/config.env-replace is licensed under MIT.

@pnpm/config.env-replace

npmv4.1.0

License MITpermissive9 versions2 maintainers0 deps9,403,036 weekly dl

pnpm/components

/ 100

Health

use with caution

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

Moderate health score (69/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

3/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/config.env-replace