Is @stdlib/complex-float64-parse safe to use?

@stdlib/complex-float64-parse has no known vulnerabilities on the latest version (0.0.3). DepScope rates its health at 55/100 (high risk).

What is the latest version of @stdlib/complex-float64-parse?

The latest version of @stdlib/complex-float64-parse is 0.0.3, released 2026-02-07.

Does @stdlib/complex-float64-parse have known vulnerabilities?

No known vulnerabilities on the latest version of @stdlib/complex-float64-parse.

Is @stdlib/complex-float64-parse deprecated?

No, @stdlib/complex-float64-parse is actively maintained. Latest release: 0.0.3 (2026-02-07).

What are alternatives to @stdlib/complex-float64-parse?

Popular alternatives to @stdlib/complex-float64-parse in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @stdlib/complex-float64-parse use?

@stdlib/complex-float64-parse is licensed under Apache-2.0.

@stdlib/complex-float64-parse

npmv0.0.3

Parse a string representation of a 128-bit complex number.

License Apache-2.0permissive3 versions4 maintainers5 deps

git://github.com/stdlib-js/complex-float64-parse

/ 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

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (5)

@stdlib/assert-is-string @stdlib/complex-float64-ctor @stdlib/string-base-replace @stdlib/string-format @stdlib/error-tools-fmtprodmsg

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@stdlib/complex-float64-parse