Is @secure-exec/nodejs safe to use?

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

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

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

Does @secure-exec/nodejs have known vulnerabilities?

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

Is @secure-exec/nodejs deprecated?

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

What are alternatives to @secure-exec/nodejs?

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

What license does @secure-exec/nodejs use?

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

@secure-exec/nodejs

npmv0.2.1

Secure Node.js execution without a sandbox. V8 isolate-based code execution with full Node.js and npm compatibility.

License Apache-2.0permissive5 versions1 maintainers8 deps26,341 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

10/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (8)

cbor-x cjs-module-lexer es-module-lexer esbuild node-stdlib-browser web-streams-polyfill @secure-exec/core @secure-exec/v8

API access

Get this data programmatically — free, no authentication.

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