super-regex

npm

Is super-regex safe to use?

The latest brin safety scan flagged super-regex v1.1.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

super-regex 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 super-regex 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.

super-regex Capabilities & Permissions

What super-regex 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 super-regex

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

super-regex Documentation & Source Code

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

Frequently asked questions about super-regex safety

Weekly Downloads

2.0M

Version

1.1.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is super-regex Safe? | npm Safety Scan - brin