Is wo-stringencoding safe to use?

wo-stringencoding has no known vulnerabilities on the latest version (0.1.1). DepScope rates its health at 14/100 (critical risk).

What is the latest version of wo-stringencoding?

The latest version of wo-stringencoding is 0.1.1, released 2014-07-25.

Does wo-stringencoding have known vulnerabilities?

No known vulnerabilities on the latest version of wo-stringencoding.

Is wo-stringencoding deprecated?

Yes, wo-stringencoding is deprecated: Moved to emailjs-stringencoding Consider using semver instead.

What are alternatives to wo-stringencoding?

Popular alternatives to wo-stringencoding in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does wo-stringencoding use?

License information for wo-stringencoding is not declared in the registry metadata.

wo-stringencoding

npmv0.1.1deprecated

Polyfill for the Encoding Living Standard's API.

1 versions3 maintainers0 deps

inexorabletash/stringencoding

/ 100

Health

find alternative

wo-stringencoding is deprecated — find an alternative

Low health score (14/100)
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/wo-stringencoding