@useprint/cli

npm

Is @useprint/cli safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @useprint/cli v0.1.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)

@useprint/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.

@useprint/cli Capabilities & Permissions

What @useprint/cli 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.

node_modules (r)/usr/ (r).env (r)node_modules (r)package.json (r)/home/ (w).env (rw)package.json (rw)+3 more

Process Spawning

This package can spawn child processes.

npm

AGENTS.md for @useprint/cli

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

@useprint/cli Documentation & Source Code

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

Frequently asked questions about @useprint/cli safety

Weekly Downloads

53

Version

0.1.1

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 @useprint/cli Safe? | npm Safety Scan - brin