cliparoo

npm

Is cliparoo safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for cliparoo v1.1.1. 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)

cliparoo 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.

cliparoo Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

AGENTS.md for cliparoo

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

cliparoo Documentation & Source Code

For the full cliparoo README, API documentation, and source code, visit the official package registry.

Frequently asked questions about cliparoo safety

Weekly Downloads

17

Version

1.1.1

License

MIT

Last Scanned

2 days ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is cliparoo Safe? | npm Safety Scan - brin