brin
brin

cli-config

npm

Is cli-config safe to use?

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

cli-config 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.

cli-config Capabilities & Permissions

What cli-config 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.

.env (rw)package.json (rw)

AGENTS.md for cli-config

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

cli-config Documentation & Source Code

For the full cli-config README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about cli-config safety

Weekly Downloads

4

Version

0.4.2

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Is cli-config Safe? | npm Safety Scan - brin