segev-cli

npm

Is segev-cli safe to use?

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

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

segev-cli Capabilities & Permissions

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

Network Access

This package makes network requests.

pokeapi.coraw.githubusercontent.com
Protocols: https

Filesystem Access

Reads and writes to the filesystem.

/usr/ (rw)

AGENTS.md for segev-cli

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

segev-cli Documentation & Source Code

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

Frequently asked questions about segev-cli safety

Weekly Downloads

16

Version

1.0.6

License

ISC

Last Scanned

2 days ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: pokeapi.co, raw.githubusercontent.com

Filesystem

Reads & Writes files

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