Is @stdlib/lapack-base-clacgv safe to use?

@stdlib/lapack-base-clacgv has no known vulnerabilities on the latest version (0.1.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of @stdlib/lapack-base-clacgv?

The latest version of @stdlib/lapack-base-clacgv is 0.1.1, released 2026-02-08.

Does @stdlib/lapack-base-clacgv have known vulnerabilities?

No known vulnerabilities on the latest version of @stdlib/lapack-base-clacgv.

Is @stdlib/lapack-base-clacgv deprecated?

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

What are alternatives to @stdlib/lapack-base-clacgv?

Popular alternatives to @stdlib/lapack-base-clacgv in npm include: ?, semver, debug, minimatch.

What license does @stdlib/lapack-base-clacgv use?

@stdlib/lapack-base-clacgv is licensed under Apache-2.0.

@stdlib/lapack-base-clacgv

npmv0.1.1

Conjugate each element in a single-precision complex floating-point vector.

License Apache-2.0permissive2 versions4 maintainers5 deps

stdlib-js/lapack-base-clacgv

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

3/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-error @stdlib/strided-base-reinterpret-complex64 @stdlib/strided-base-stride2offset @stdlib/utils-define-nonenumerable-read-only-property @stdlib/utils-try-require

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@stdlib/lapack-base-clacgv