Is @stdlib/string-replace-cli safe to use?

@stdlib/string-replace-cli has no known vulnerabilities on the latest version (0.2.3). DepScope rates its health at 55/100 (high risk).

What is the latest version of @stdlib/string-replace-cli?

The latest version of @stdlib/string-replace-cli is 0.2.3, released 2026-02-08.

Does @stdlib/string-replace-cli have known vulnerabilities?

No known vulnerabilities on the latest version of @stdlib/string-replace-cli.

Is @stdlib/string-replace-cli deprecated?

No, @stdlib/string-replace-cli is actively maintained. Latest release: 0.2.3 (2026-02-08).

What are alternatives to @stdlib/string-replace-cli?

Popular alternatives to @stdlib/string-replace-cli in npm include: debug, semver, ansi-styles, minimatch, brace-expansion.

What license does @stdlib/string-replace-cli use?

@stdlib/string-replace-cli is licensed under Apache-2.0.

@stdlib/string-replace-cli

npmv0.2.3

Replace search occurrences with a replacement string.

License Apache-2.0permissive6 versions4 maintainers9 deps

git://github.com/stdlib-js/string-replace

/ 100

Health

safe to use

@stdlib/[email protected] is safe to use (health: 55/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (9)

@stdlib/assert-is-regexp @stdlib/assert-is-regexp-string @stdlib/cli-ctor @stdlib/fs-read-file @stdlib/process-read-stdin @stdlib/regexp-eol @stdlib/streams-node-stdin @stdlib/utils-regexp-from-string @stdlib/string-replace

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@stdlib/string-replace-cli