noba-assistant-chat

npm

Is noba-assistant-chat safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for noba-assistant-chat v0.1.0-canary.30. 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)

noba-assistant-chat 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.

noba-assistant-chat Capabilities & Permissions

What noba-assistant-chat 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.

github.comhtml.spec.whatwg.orgnodejs.orgwww.ibm.comwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for noba-assistant-chat

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

noba-assistant-chat Documentation & Source Code

For the full noba-assistant-chat README, API documentation, and source code, visit the official package registry.

Frequently asked questions about noba-assistant-chat safety

Weekly Downloads

31

Version

0.1.0-canary.30

License

ISC

Last Scanned

8 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, html.spec.whatwg.org, nodejs.org...

Process

Spawns child processes