@chorus-one/monad

npm

Is @chorus-one/monad safe to use?

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

@chorus-one/monad 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.

@chorus-one/monad Capabilities & Permissions

What @chorus-one/monad can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

TEST_MONAD_MNEMONICTEST_MONAD_RPC_URL

AGENTS.md for @chorus-one/monad

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

@chorus-one/monad Documentation & Source Code

For the full @chorus-one/monad README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @chorus-one/monad safety

Weekly Downloads

120

Version

1.0.4

License

Apache-2.0

Last Scanned

5 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: TEST_MONAD_MNEMONIC, TEST_MONAD_RPC_URL

Is @chorus-one/monad Safe? | npm Safety Scan - brin