Is browser-string-hexer safe to use?

browser-string-hexer has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 36/100 (critical risk).

What is the latest version of browser-string-hexer?

The latest version of browser-string-hexer is 1.0.0, released 2022-01-30.

Does browser-string-hexer have known vulnerabilities?

No known vulnerabilities on the latest version of browser-string-hexer.

Is browser-string-hexer deprecated?

No, browser-string-hexer is actively maintained. Latest release: 1.0.0 (2022-01-30).

What are alternatives to browser-string-hexer?

Popular alternatives to browser-string-hexer in npm include: ?, semver, ansi-styles, minimatch, debug.

What license does browser-string-hexer use?

browser-string-hexer is licensed under MIT.

browser-string-hexer

npmv1.0.0

A simple function for encoding a utf-8 string as a hex string.

License MITpermissive1 versions1 maintainers142 deps26 weekly dl

danfinlay/browser-string-hexer

/ 100

Health

use with caution

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

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.5 KBminified

0.3 KB gzipped

142 direct dependencies

side effects

🌟

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/browser-string-hexer