sanitize-filename

PyPI

Is sanitize-filename safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for sanitize-filename v1.2.0. Trust score: 85/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

sanitize-filename Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

sanitize-filename Capabilities & Permissions

What sanitize-filename can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

AGENTS.md for sanitize-filename

Good instructions lead to good results. brin adds sanitize-filename documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

sanitize-filename Documentation & Source Code

For the full sanitize-filename README, API documentation, and source code, visit the official package registry.

Frequently asked questions about sanitize-filename safety

Weekly Downloads

71.6K

Version

1.2.0

License

WTFPL OR ISC

Other Versions

Last Scanned

Feb 9, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is sanitize-filename Safe? | npm Safety Scan - brin