Is @putout/engine-processor safe to use?

@putout/engine-processor has no known vulnerabilities on the latest version (16.0.0). DepScope rates its health at 67/100 (moderate risk).

What is the latest version of @putout/engine-processor?

The latest version of @putout/engine-processor is 16.0.0, released 2026-01-02.

Does @putout/engine-processor have known vulnerabilities?

No known vulnerabilities on the latest version of @putout/engine-processor.

Is @putout/engine-processor deprecated?

No, @putout/engine-processor is actively maintained. Latest release: 16.0.0 (2026-01-02).

What are alternatives to @putout/engine-processor?

Popular alternatives to @putout/engine-processor in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @putout/engine-processor use?

@putout/engine-processor is licensed under MIT.

@putout/engine-processor

npmv16.0.0

🐊Putout engine processor runner

License MITpermissive53 versions1 maintainers4 deps24,081 weekly dl

coderaiser/putout

/ 100

Health

use with caution

@putout/[email protected] low health (67/100) — consider alternatives

Moderate health score (67/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

@putout/engine-loader once picomatch try-to-catch

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@putout/engine-processor