@hoevelmanns/vcli

npm

Is @hoevelmanns/vcli safe to use?

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

@hoevelmanns/vcli 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.

@hoevelmanns/vcli Capabilities & Permissions

What @hoevelmanns/vcli can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads and writes to the filesystem.

package.json (rw)

Process Spawning

This package can spawn child processes.

AGENTS.md for @hoevelmanns/vcli

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

@hoevelmanns/vcli Documentation & Source Code

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

Frequently asked questions about @hoevelmanns/vcli safety

Weekly Downloads

70

Version

1.3.30

License

MIT

Last Scanned

1 day ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is @hoevelmanns/vcli Safe? | npm Safety Scan - brin