inline-critical

npm

Is inline-critical safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for inline-critical v12.1.0. 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)

inline-critical 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.

inline-critical Capabilities & Permissions

What inline-critical 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.

AGENTS.md for inline-critical

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

inline-critical Documentation & Source Code

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

Frequently asked questions about inline-critical safety

Weekly Downloads

34.4K

Version

12.1.0

License

MIT

Last Scanned

2 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is inline-critical Safe? | npm Safety Scan - brin