@thomasyzt/lvui

npm

Is @thomasyzt/lvui safe to use?

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

@thomasyzt/lvui 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.

@thomasyzt/lvui Capabilities & Permissions

What @thomasyzt/lvui 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.

feross.org>mths.beopen.weixin.qq.comwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for @thomasyzt/lvui

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

@thomasyzt/lvui Documentation & Source Code

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

Frequently asked questions about @thomasyzt/lvui safety

Weekly Downloads

28

Version

1.4.2

Last Scanned

1 day ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: feross.org>, mths.be, open.weixin.qq.com...

Process

Spawns child processes

Is @thomasyzt/lvui Safe? | npm Safety Scan - brin