brin
brin

alias

npm

Is alias safe to use?

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

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

alias Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

/etc/ (r)/etc/ (r)/etc/ (r)/etc/ (r)

AGENTS.md for alias

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

alias Documentation & Source Code

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

View on npmView Source

Frequently asked questions about alias safety

Weekly Downloads

181

Version

0.0.5

License

MIT

Last Scanned

21 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is alias Safe? | npm Safety Scan - brin