mailpurify

npm

Is mailpurify safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for mailpurify v0.1.5. Trust score: 55/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)

mailpurify 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.

mailpurify Capabilities & Permissions

No system capabilities detected for mailpurify. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for mailpurify

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

mailpurify Documentation & Source Code

For the full mailpurify README, API documentation, and source code, visit the official package registry.

Frequently asked questions about mailpurify safety

Weekly Downloads

16

Version

0.1.5

License

MIT

Last Scanned

1 day ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is mailpurify Safe? | npm Safety Scan - brin