@lexical/code

npm

Is @lexical/code safe to use?

The latest brin safety scan flagged @lexical/code v0.40.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

@lexical/code Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • Can spawn child processes

brin Recommendations

  • This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add @lexical/code to automatically apply these checks before installation.

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.

@lexical/code Capabilities & Permissions

What @lexical/code 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.

NODE_ENV

AGENTS.md for @lexical/code

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

@lexical/code Documentation & Source Code

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

Frequently asked questions about @lexical/code safety

Weekly Downloads

1.7M

Version

0.40.0

License

MIT

Other Versions

Last Scanned

Feb 3, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: NODE_ENV

Is @lexical/code Safe? | npm Safety Scan - brin