file-saver

npm

Is file-saver safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for file-saver v2.0.5. Trust score: 75/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)

file-saver 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.

file-saver Capabilities & Permissions

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

Network Access

This package makes network requests.

eligrey.comgithub.compurl.eligrey.comstackoverflow.comwww.whatismybrowser.com
Protocols: http, https

AGENTS.md for file-saver

Good instructions lead to good results. brin adds file-saver 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 →

file-saver Documentation & Source Code

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

Frequently asked questions about file-saver safety

Weekly Downloads

5.1M

Version

2.0.5

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: eligrey.com, github.com, purl.eligrey.com...

Is file-saver Safe? | npm Safety Scan - brin