brin
brin

is-ascii-safe-cli

npm

Is is-ascii-safe-cli safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for is-ascii-safe-cli v1.0.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)

is-ascii-safe-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.

is-ascii-safe-cli Capabilities & Permissions

What is-ascii-safe-cli can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

/usr/ (r)package.json (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for is-ascii-safe-cli

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

is-ascii-safe-cli Documentation & Source Code

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

View on npmView Source

Frequently asked questions about is-ascii-safe-cli safety

Weekly Downloads

25

Version

1.0.1

License

Apache-2.0

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is is-ascii-safe-cli Safe? | npm Safety Scan - brin