@jsenv/assert

npm

Is @jsenv/assert safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @jsenv/assert v4.5.5. 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)

@jsenv/assert 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.

@jsenv/assert Capabilities & Permissions

What @jsenv/assert 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.

CAPTURING_SIDE_EFFECTSFORCE_COLORFORCE_UNICODEGITHUB_WORKFLOW

AGENTS.md for @jsenv/assert

Good instructions lead to good results. brin adds @jsenv/assert 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 →

@jsenv/assert Documentation & Source Code

For the full @jsenv/assert README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @jsenv/assert safety

Weekly Downloads

356

Version

4.5.5

License

MIT

Last Scanned

3 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: CAPTURING_SIDE_EFFECTS, FORCE_COLOR, FORCE_UNICODE...

Is @jsenv/assert Safe? | npm Safety Scan - brin