Is @cjser/is-safe-filename safe to use?

@cjser/is-safe-filename has no known vulnerabilities on the latest version (0.1.1-cjser.2). DepScope rates its health at 47/100 (high risk).

What is the latest version of @cjser/is-safe-filename?

The latest version of @cjser/is-safe-filename is 0.1.1-cjser.2, released 2026-05-07.

Does @cjser/is-safe-filename have known vulnerabilities?

No known vulnerabilities on the latest version of @cjser/is-safe-filename.

Is @cjser/is-safe-filename deprecated?

No, @cjser/is-safe-filename is actively maintained. Latest release: 0.1.1-cjser.2 (2026-05-07).

What are alternatives to @cjser/is-safe-filename?

Popular alternatives to @cjser/is-safe-filename in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @cjser/is-safe-filename use?

@cjser/is-safe-filename is licensed under MIT.

@cjser/is-safe-filename

npmv0.1.1-cjser.2

Check if a filename is safe to use in a path join operation

License MITpermissive1 versions1 maintainers0 deps5 weekly dl

https://code.moenext.com/3rdeye/cjser

/ 100

Health

use with caution

@cjser/[email protected] low health (47/100) — consider alternatives

Moderate health score (47/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@cjser/is-safe-filename