oc-client

npm

Is oc-client safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for oc-client v4.0.2. 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)

oc-client 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.

oc-client Capabilities & Permissions

What oc-client 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.

cdn.commy-registry.comwww.registries.com
Protocols: http, https

AGENTS.md for oc-client

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

oc-client Documentation & Source Code

For the full oc-client README, API documentation, and source code, visit the official package registry.

Frequently asked questions about oc-client safety

Weekly Downloads

5.5K

Version

4.0.2

License

MIT

Last Scanned

2 hours ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: cdn.com, my-registry.com, www.registries.com

Is oc-client Safe? | npm Safety Scan - brin