Is @dazl/engine-runtime-node safe to use?

@dazl/engine-runtime-node has no known vulnerabilities on the latest version (52.1.0). DepScope rates its health at 65/100 (moderate risk).

What is the latest version of @dazl/engine-runtime-node?

The latest version of @dazl/engine-runtime-node is 52.1.0, released 2026-03-16.

Does @dazl/engine-runtime-node have known vulnerabilities?

No known vulnerabilities on the latest version of @dazl/engine-runtime-node.

Is @dazl/engine-runtime-node deprecated?

No, @dazl/engine-runtime-node is actively maintained. Latest release: 52.1.0 (2026-03-16).

What are alternatives to @dazl/engine-runtime-node?

Popular alternatives to @dazl/engine-runtime-node in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @dazl/engine-runtime-node use?

@dazl/engine-runtime-node is licensed under MIT.

@dazl/engine-runtime-node

npmv52.1.0

Tools for running engine environments in node

License MITpermissive19 versions35 maintainers10 deps1,910 weekly dl

dazl-dev/engine

/ 100

Health

safe to use

@dazl/[email protected] is safe to use (health: 65/100)

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (10)

cors express minimist socket.io @dazl/common @dazl/patterns @dazl/engine-core @file-services/node @dazl/isomorphic-worker create-listening-server

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@dazl/engine-runtime-node