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

@stdlib/complex-float64-reviver 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-reviver?

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

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

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

Is @stdlib/complex-float64-reviver deprecated?

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

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

Popular alternatives to @stdlib/complex-float64-reviver in npm include: debug, lru-cache, string-width, commander, picomatch.

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

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

@stdlib/complex-float64-reviver

npmv0.0.3

Revive a JSON-serialized 128-bit complex number.

License Apache-2.0permissive3 versions4 maintainers2 deps16 weekly dl

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

/ 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

📦

Bundle Size

8.9 KBminified

3.2 KB gzipped

2 direct dependencies

side effectsscoped

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@stdlib/assert-is-number @stdlib/complex-float64-ctor

API access

Get this data programmatically — free, no authentication.

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