iobroker.email

npm

Is iobroker.email safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for iobroker.email v2.0.4. 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)

iobroker.email 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.

iobroker.email Capabilities & Permissions

What iobroker.email 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.

developer.mozilla.orgfb.megithub.commodule-federation.iomui.comoauth2.iobroker.inreactjs.orgwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for iobroker.email

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

iobroker.email Documentation & Source Code

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

Frequently asked questions about iobroker.email safety

Weekly Downloads

278

Version

2.0.4

License

MIT

Last Scanned

2 days ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: developer.mozilla.org, fb.me, github.com...

Process

Spawns child processes