Is gulp-string-replace safe to use?

gulp-string-replace has no known vulnerabilities on the latest version (1.1.2). DepScope rates its health at 52/100 (high risk).

What is the latest version of gulp-string-replace?

The latest version of gulp-string-replace is 1.1.2, released 2018-10-12.

Does gulp-string-replace have known vulnerabilities?

No known vulnerabilities on the latest version of gulp-string-replace.

Is gulp-string-replace deprecated?

No, gulp-string-replace is actively maintained. Latest release: 1.1.2 (2018-10-12).

What are alternatives to gulp-string-replace?

Popular alternatives to gulp-string-replace in npm include: ?, semver, debug, minimatch.

What license does gulp-string-replace use?

gulp-string-replace is licensed under MIT.

gulp-string-replace

npmv1.1.2

Replace strings in files by using string or regex patterns.

License MITpermissive11 versions1 maintainers6 deps12,608 weekly dl

tomaszczechowski/gulp-string-replace

/ 100

Health

use with caution

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

Moderate health score (52/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

15/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)

chalk extend fancy-log plugin-error replacestream through2

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/gulp-string-replace