consistent-env

npm

Is consistent-env safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for consistent-env v1.3.1. Trust score: 75/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)

consistent-env 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.

consistent-env Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

PATHSHELLUSER

AGENTS.md for consistent-env

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

consistent-env Documentation & Source Code

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

Frequently asked questions about consistent-env safety

Weekly Downloads

264

Version

1.3.1

License

MIT

Last Scanned

7 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: PATH, SHELL, USER

Is consistent-env Safe? | npm Safety Scan - brin