Is sanitize-filename safe to use?

sanitize-filename has no known vulnerabilities on the latest version (1.6.4). DepScope rates its health at 81/100 (low risk).

What is the latest version of sanitize-filename?

The latest version of sanitize-filename is 1.6.4, released 2026-03-20.

Does sanitize-filename have known vulnerabilities?

No known vulnerabilities on the latest version of sanitize-filename.

Is sanitize-filename deprecated?

No, sanitize-filename is actively maintained. Latest release: 1.6.4 (2026-03-20).

What are alternatives to sanitize-filename?

Popular alternatives to sanitize-filename in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does sanitize-filename use?

sanitize-filename is licensed under WTFPL OR ISC.

sanitize-filename

npmv1.6.4

Sanitize a string for use as a filename

License WTFPL OR ISCpermissive23 versions1 maintainers1 deps6,301,225 weekly dl

parshap/node-sanitize-filename

/ 100

Health

safe to use

[email protected] is safe to use (health: 81/100)

Health breakdown0 – 100

20/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

4/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.3 KBminified

0.7 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

10/10typed

bundled

Quality signals

OSS Criticality

0.69high

Health History

Dependency Tree

License Audit

Dependencies (1)

truncate-utf8-bytes

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/sanitize-filename