brin
brin

editorconfig

npm

Is editorconfig safe to use?

The latest brin safety scan flagged editorconfig v3.0.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

editorconfig 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 editorconfig 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.

editorconfig Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

package.json (r)package.json (r)package.json (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for editorconfig

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

editorconfig Documentation & Source Code

For the full editorconfig README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about editorconfig safety

Weekly Downloads

7.1M

Version

3.0.1

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is editorconfig Safe? | npm Safety Scan - brin