lazy-strict-env

npm

Is lazy-strict-env safe to use?

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

lazy-strict-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.

lazy-strict-env Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

PATH

AGENTS.md for lazy-strict-env

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

lazy-strict-env Documentation & Source Code

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

Frequently asked questions about lazy-strict-env safety

Weekly Downloads

80

Version

0.3.1

Last Scanned

14 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: PATH

Is lazy-strict-env Safe? | npm Safety Scan - brin