Is sanitize-contents safe to use?

sanitize-contents has no known vulnerabilities on the latest version (1.0.3). DepScope rates its health at 45/100 (high risk).

What is the latest version of sanitize-contents?

The latest version of sanitize-contents is 1.0.3, released 2026-01-09.

Does sanitize-contents have known vulnerabilities?

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

Is sanitize-contents deprecated?

No, sanitize-contents is actively maintained. Latest release: 1.0.3 (2026-01-09).

What are alternatives to sanitize-contents?

Popular alternatives to sanitize-contents in npm include: minimatch, commander, eslint-visitor-keys, ajv, color-name.

What license does sanitize-contents use?

sanitize-contents is licensed under ISC.

sanitize-contents

npmv1.0.3

A robust, lightweight, and customizable library to sanitize/redact sensitive information (passwords, tokens, API keys, connection strings) from strings and HTML content.

License ISCpermissive4 versions1 maintainers2 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@types/jsdom jsdom

API access

Get this data programmatically — free, no authentication.

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