Is @monstermann/unplugin-tree-shake-import-namespaces safe to use?

@monstermann/unplugin-tree-shake-import-namespaces has no known vulnerabilities on the latest version (0.4.0). DepScope rates its health at 48/100 (high risk).

Does @monstermann/unplugin-tree-shake-import-namespaces have known vulnerabilities?

No known vulnerabilities on the latest version of @monstermann/unplugin-tree-shake-import-namespaces.

Is @monstermann/unplugin-tree-shake-import-namespaces deprecated?

No, @monstermann/unplugin-tree-shake-import-namespaces is actively maintained. Latest release: 0.4.0 (2026-02-15).

What are alternatives to @monstermann/unplugin-tree-shake-import-namespaces?

Popular alternatives to @monstermann/unplugin-tree-shake-import-namespaces in npm include: ?, semver, ansi-styles, minimatch, debug.

What license does @monstermann/unplugin-tree-shake-import-namespaces use?

@monstermann/unplugin-tree-shake-import-namespaces is licensed under MIT.

@monstermann/unplugin-tree-shake-import-namespaces

npmv0.4.0

Tree-shake import namespaces with oxc.

License MITpermissive8 versions1 maintainers3 deps7 weekly dl

MichaelOstermann/tree-shake-import-namespaces

/ 100

Health

use with caution

@monstermann/[email protected] low health (48/100) — consider alternatives

Moderate health score (48/100) — verify manually

Health breakdown0 – 100

15/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 (3)

@monstermann/tree-shake-import-namespaces unplugin unplugin-utils

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@monstermann/unplugin-tree-shake-import-namespaces