Is @stdlib/complex-float32-base-neg safe to use?

@stdlib/complex-float32-base-neg has no known vulnerabilities on the latest version (0.1.1). DepScope rates its health at 52/100 (high risk).

What is the latest version of @stdlib/complex-float32-base-neg?

The latest version of @stdlib/complex-float32-base-neg is 0.1.1, released 2026-02-08.

No known vulnerabilities on the latest version of @stdlib/complex-float32-base-neg.

No, @stdlib/complex-float32-base-neg is actively maintained. Latest release: 0.1.1 (2026-02-08).

Popular alternatives to @stdlib/complex-float32-base-neg in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

@stdlib/complex-float32-base-neg is licensed under Apache-2.0.

npmv0.1.1

Negate a single-precision complex floating-point number.

License Apache-2.0permissive2 versions4 maintainers6 deps13 weekly dl

/ 100

Health

safe to use

@stdlib/[email protected] is safe to use (health: 52/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

4/15

community

Vulnerabilities

none known

🌟

10/10typed

bundled

Dependencies (6)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@stdlib/complex-float32-base-neg