@o/ui

npm

Is @o/ui safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @o/ui v2.8.23. Trust score: 50/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)

@o/ui 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.

@o/ui Capabilities & Permissions

What @o/ui 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.compopmotion.ioprojects.lukehaas.meraw.githubusercontent.comwww.w3.org
Protocols: http, https

Environment Variables

Accesses the following environment variables.

NODE_ENVRENDER_TARGETSPLIT_CHUNKS

AGENTS.md for @o/ui

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

@o/ui Documentation & Source Code

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

Frequently asked questions about @o/ui safety

Weekly Downloads

54

Version

2.8.23

License

MIT

Last Scanned

15 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, popmotion.io, projects.lukehaas.me...

Environment

Accesses: NODE_ENV, RENDER_TARGET, SPLIT_CHUNKS

Is @o/ui Safe? | npm Safety Scan - brin