Is @secure-exec/v8 safe to use?

@secure-exec/v8 has no known vulnerabilities on the latest version (0.2.1). DepScope rates its health at 53/100 (high risk).

What is the latest version of @secure-exec/v8?

The latest version of @secure-exec/v8 is 0.2.1, released 2026-03-31.

Does @secure-exec/v8 have known vulnerabilities?

No known vulnerabilities on the latest version of @secure-exec/v8.

Is @secure-exec/v8 deprecated?

No, @secure-exec/v8 is actively maintained. Latest release: 0.2.1 (2026-03-31).

What are alternatives to @secure-exec/v8?

Popular alternatives to @secure-exec/v8 in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @secure-exec/v8 use?

@secure-exec/v8 is licensed under Apache-2.0.

@secure-exec/v8

npmv0.2.1

V8 runtime process for Secure Exec — embeds V8 via Rust (rusty_v8) and communicates over Unix domain socket with length-prefixed MessagePack IPC.

License Apache-2.0permissive8 versions1 maintainers1 deps

rivet-dev/secure-exec

/ 100

Health

safe to use

@secure-exec/[email protected] is safe to use (health: 53/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

cbor-x

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@secure-exec/v8