brin
brin

oo-cli

npm

Is oo-cli safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for oo-cli v0.2.1. Trust score: 65/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)

oo-cli 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.

oo-cli Capabilities & Permissions

What oo-cli can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Writes to the filesystem.

.env (w)package.json (w)/usr/ (w)/usr/ (w)/usr/ (w)/usr/ (w).env (w)package.json (w)+2 more

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for oo-cli

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

oo-cli Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about oo-cli safety

Weekly Downloads

144

Version

0.2.1

License

MIT

Last Scanned

2 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files

Environment

Accesses: NODE_ENV

Is oo-cli Safe? | npm Safety Scan - brin