Is @cjser/unused-filename safe to use?

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

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

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

Does @cjser/unused-filename have known vulnerabilities?

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

Is @cjser/unused-filename deprecated?

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

What are alternatives to @cjser/unused-filename?

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

What license does @cjser/unused-filename use?

@cjser/unused-filename is licensed under MIT.

@cjser/unused-filename

npmv4.0.1-cjser.2

Get an unused filename by appending a number if it exists: `file.txt` → `file (1).txt`

License MITpermissive1 versions1 maintainers2 deps

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

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

@cjser/escape-string-regexp @cjser/path-exists

API access

Get this data programmatically — free, no authentication.

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