brin
brin

@iota/iota.js

npm

Is @iota/iota.js safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @iota/iota.js v1.8.6. 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)

@iota/iota.js 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.

@iota/iota.js Capabilities & Permissions

What @iota/iota.js 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.

oeis.org
Protocols: https

Process Spawning

This package can spawn child processes.

AGENTS.md for @iota/iota.js

Good instructions lead to good results. brin adds @iota/iota.js 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 →

@iota/iota.js Documentation & Source Code

For the full @iota/iota.js README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about @iota/iota.js safety

Weekly Downloads

174

Version

1.8.6

License

Apache-2.0

Last Scanned

3 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: oeis.org

Process

Spawns child processes

Is @iota/iota.js Safe? | npm Safety Scan - brin