Is @stdlib/complex-reviver safe to use?

@stdlib/complex-reviver has no known vulnerabilities on the latest version (0.2.3). DepScope rates its health at 53/100 (high risk).

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

The latest version of @stdlib/complex-reviver is 0.2.3, released 2026-02-08.

Does @stdlib/complex-reviver have known vulnerabilities?

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

Is @stdlib/complex-reviver deprecated?

No, @stdlib/complex-reviver is actively maintained. Latest release: 0.2.3 (2026-02-08).

What are alternatives to @stdlib/complex-reviver?

Popular alternatives to @stdlib/complex-reviver in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @stdlib/complex-reviver use?

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

@stdlib/complex-reviver

npmv0.2.3

Revive a JSON-serialized complex number.

License Apache-2.0permissive12 versions4 maintainers3 deps42 weekly dl

stdlib-js/complex-reviver

/ 100

Health

use with caution

@stdlib/[email protected] low health (53/100) — consider alternatives

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

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

API access

Get this data programmatically — free, no authentication.

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